<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/agentforce-vibes--w0pelzlfa" -->

---
title: 開発の意図に応じてツールを自動で選択 – Agentforce Vibesの新機能「アビリティ」 | daily.dev
description: Agentforce Vibes introduces a new feature called Abilities, an intelligent context-activation system that automatically selects the most relevant Salesforce DX...
canonical: https://daily.dev/posts/agentforce-vibes--w0pelzlfa
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: 開発の意図に応じてツールを自動で選択 – Agentforce Vibesの新機能「アビリティ」 | daily.dev
og:description: Agentforce Vibes introduces a new feature called Abilities, an intelligent context-activation system that automatically selects the most relevant Salesforce DX...
og:url: https://daily.dev/posts/agentforce-vibes--w0pelzlfa
og:image: https://api.daily.dev/og/posts/w0peLZLfA.png
og:image:alt: 開発の意図に応じてツールを自動で選択 – Agentforce Vibesの新機能「アビリティ」
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# 開発の意図に応じてツールを自動で選択 – Agentforce Vibesの新機能「アビリティ」

**[Salesforce Developers Blog](https://daily.dev/sources/salesforcedevs)** · 1 min read · 0 upvotes · 0 comments

## Summary

Agentforce Vibes introduces a new feature called Abilities, an intelligent context-activation system that automatically selects the most relevant Salesforce DX MCP Server tools for a given coding task, instead of requiring developers to manually configure a mcp_config.json file. With over 80 available MCP tools, enabling all of them bloats prompts and degrades output quality, while too few tools cause failures. Abilities groups tools by domain (Apex/LWC development, DevOps, mobile development, core platform admin) and uses RAG-based semantic search: tool definitions are vector-embedded and indexed, prompts are embedded and compared via cosine similarity, and the top ~10 matching tools are loaded into the model's execution context. An orchestration layer called the Ability Coordinator also adds dependent tools when an orchestrator tool is selected, preventing execution failures from missing dependencies. Abilities work alongside Skills, which define reusable step-by-step task procedures, with Abilities deciding what tools are available and Skills defining how work gets done. Planned enhancements include broader support for first- and third-party MCP servers and improved dependency detection.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://developer.salesforce.com/blogs/2026/09/intent-driven-tool-selection-using-abilities-in-agentforce-vibes-jp>

## Questions this post answers

### How does Agentforce Vibes decide which Salesforce DX MCP Server tools to enable for a given request?

Agentforce Vibes uses a feature called Abilities, which relies on RAG-based semantic search rather than exposing all available tools. Tool definitions are vector-embedded and indexed in a vector database, the developer's prompt is embedded with the same model, a cosine similarity search runs against the index, and roughly the top 10 most relevant tools are loaded into the model's execution context as a temporary function catalog.

_Developers tuning AI agent tool selection can track updates like this on daily.dev._

### Why does enabling all Salesforce DX MCP Server tools at once hurt AI coding agent output?

Enabling all available tools at once bloats the prompt, gives the model too many options, lowers output quality, and increases token costs. Salesforce DX MCP Server exposes over 80 tools covering CLI commands, testing, code analysis, accessibility checks, DevOps operations, and mobile development, so Salesforce enables only a subset by default, though too few tools can also block tasks like Apex generation or LWC refactoring.

_Anyone configuring MCP tool sets for coding agents can follow lessons like this via daily.dev._

### What happens when an MCP orchestrator tool is selected but its dependent tools are missing?

Some MCP tools act as orchestrators that coordinate a workflow and require additional tools to complete a task; if semantic search retrieves only the orchestrator tool, execution can fail due to missing dependencies. Abilities addresses this by automatically adding the required dependent tools after the initial tool selection, keeping the overall tool set small while still supplying everything needed to finish the task.

_Teams debugging MCP tool dependency failures can keep up with fixes like this through daily.dev._

## Similar posts on daily.dev

- [Intent-Driven Tool Selection Using Abilities in Agentforce Vibes](https://daily.dev/posts/intent-driven-tool-selection-using-abilities-in-agentforce-vibes-4ogfpndx4) · Salesforce Developers Blog · 1 upvotes · 0 comments
- [Salesforce DX MCPを使った、Lightning Webコンポーネントのバイブコーディング](https://daily.dev/posts/salesforce-dx-mcp-lightning-web--3l3fxl6ms) · Salesforce Developers Blog · 0 upvotes · 0 comments
- [From Abilities to AI Agents: Introducing the WordPress MCP Adapter](https://daily.dev/posts/from-abilities-to-ai-agents-introducing-the-wordpress-mcp-adapter-fscy7oxf8) · WordPress Developer · 2 upvotes · 0 comments
- [“Six tools, one harness”: Salesforce loops together a six-pack of favorites](https://daily.dev/posts/six-tools-one-harness-salesforce-loops-together-a-six-pack-of-favorites-a936j1oy5) · The New Stack · 1 upvotes · 0 comments

---

Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#mcp](https://daily.dev/tags/mcp), [#rag](https://daily.dev/tags/rag), [#salesforce](https://daily.dev/tags/salesforce)

[View this post on daily.dev](https://daily.dev/posts/agentforce-vibes--w0pelzlfa)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"開発の意図に応じてツールを自動で選択 – Agentforce Vibesの新機能「アビリティ」","url":"https://daily.dev/posts/agentforce-vibes--w0pelzlfa","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/agentforce-vibes--w0pelzlfa"},"datePublished":"2026-09-16T08:23:57.083Z","dateModified":"2026-09-16T08:29:57.708Z","description":"Agentforce Vibes introduces a new feature called Abilities, an intelligent context-activation system that automatically selects the most relevant Salesforce DX...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/db5327b80a23d03eb5848f6f2ff15a58?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/db5327b80a23d03eb5848f6f2ff15a58?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Salesforce Developers Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Salesforce Developers Blog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/662fb7dc7cd14ee59747ed58d75cf7c3","url":"https://daily.dev/sources/salesforcedevs"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/agentforce-vibes--w0pelzlfa","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,mcp,rag,salesforce","timeRequired":"PT1M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Salesforce Developers Blog","item":"https://daily.dev/sources/salesforcedevs"},{"@type":"ListItem","position":3,"name":"開発の意図に応じてツールを自動で選択 – Agentforce Vibesの新機能「アビリティ」"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/agentforce-vibes--w0pelzlfa#faq","mainEntity":[{"@type":"Question","name":"How does Agentforce Vibes decide which Salesforce DX MCP Server tools to enable for a given request?","acceptedAnswer":{"@type":"Answer","text":"Agentforce Vibes uses a feature called Abilities, which relies on RAG-based semantic search rather than exposing all available tools. Tool definitions are vector-embedded and indexed in a vector database, the developer's prompt is embedded with the same model, a cosine similarity search runs against the index, and roughly the top 10 most relevant tools are loaded into the model's execution context as a temporary function catalog. Developers tuning AI agent tool selection can track updates like this on daily.dev."}},{"@type":"Question","name":"Why does enabling all Salesforce DX MCP Server tools at once hurt AI coding agent output?","acceptedAnswer":{"@type":"Answer","text":"Enabling all available tools at once bloats the prompt, gives the model too many options, lowers output quality, and increases token costs. Salesforce DX MCP Server exposes over 80 tools covering CLI commands, testing, code analysis, accessibility checks, DevOps operations, and mobile development, so Salesforce enables only a subset by default, though too few tools can also block tasks like Apex generation or LWC refactoring. Anyone configuring MCP tool sets for coding agents can follow lessons like this via daily.dev."}},{"@type":"Question","name":"What happens when an MCP orchestrator tool is selected but its dependent tools are missing?","acceptedAnswer":{"@type":"Answer","text":"Some MCP tools act as orchestrators that coordinate a workflow and require additional tools to complete a task; if semantic search retrieves only the orchestrator tool, execution can fail due to missing dependencies. Abilities addresses this by automatically adding the required dependent tools after the initial tool selection, keeping the overall tool set small while still supplying everything needed to finish the task. Teams debugging MCP tool dependency failures can keep up with fixes like this through daily.dev."}}]}
```

