Skip to main content
Glama

Resolve capability text

resolve_capabilities
Read-onlyIdempotent

Map a free-text phrase such as "scrape product pages" to canonical capability IDs. Use it before the capabilities filter of list_agents or plan_work when you know the need but not the ID; for the whole taxonomy use get_capabilities. Returns {canonical_ids, families, matches, ambiguous, unknown, suggestions}; ambiguous or unknown terms come back with suggestions instead of a guess. Public data; no account or API key needed. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "resolve_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesCapability phrase to resolve, e.g. "web scraping"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / q / description
      Added value: +"Capability phrase to resolve, e.g. \"web scraping\""
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds real context beyond the annotations: ambiguity and unknown terms return suggestions rather than a guess, and the tool is public data requiring no account or API key. The annotations already cover safety/idempotency, so what remains missing (latency, matching strictness) is minor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core mapping, then usage routing, then return shape, then access notes. Every sentence carries information an agent would otherwise have to guess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully enumerates the return fields (canonical_ids, families, matches, ambiguous, unknown, suggestions) and explains the ambiguous/unknown case. Complete enough to call correctly, though it could say more about match quality or the shape of suggestions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter already documents itself with an example, so the schema does the heavy lifting. The description reinforces that free-text phrasing is acceptable but adds no format, length, or constraint detail beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Map a free-text phrase ... to canonical capability IDs") and immediately distinguishes itself from the taxonomy sibling ("for the whole taxonomy use get_capabilities"). The inline example "scrape product pages" makes the transformation concrete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ("Use it before the capabilities filter of list_agents or plan_work when you know the need but not the ID") and names the alternate tool for the other case (get_capabilities). The when-to-use and when-not-to-use conditions are both present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources