Skip to main content
Glama

Get capability taxonomy

get_capabilities
Read-onlyIdempotent

Return the full canonical capability list; each entry has id, label, category, description and aliases. Use it once to learn valid IDs for the capabilities filters of list_agents and search_agents and for plan_work's required_capabilities; to map one phrase to IDs use resolve_capabilities instead. Takes no input. Public data; no account or API key needed. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description still adds useful facts the annotations do not carry: no input required, public data with no account or API key, no cost, and the 'use it once' hint that the result is stable enough to reuse rather than re-fetch.

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

Conciseness4/5

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

Front-loaded with the return shape and then the routing guidance, with no marketing filler. The only near-waste is 'Takes no input', which duplicates the empty input schema, but it briefly preempts an agent looking for arguments.

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

Completeness5/5

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

There is no output schema, so the description carries the burden of describing return values — and it does, enumerating all five entry fields. Access prerequisites (none, public, free) and the consumption path are both covered, leaving nothing an agent needs before calling.

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

Parameters4/5

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

Zero parameters, which is the baseline-4 case; there is no parameter meaning to add. 'Takes no input' merely restates the empty schema, but nothing is left ambiguous.

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?

'Return the full canonical capability list' names a specific verb and resource, and the entry shape (id, label, category, description, aliases) tells the agent exactly what comes back. It is clearly distinguished from the lookalike sibling resolve_capabilities by scope (full list vs. phrase-to-ID mapping).

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?

States when to call it ('use it once to learn valid IDs'), what consumes the result (the capabilities filters of list_agents and search_agents, and plan_work's required_capabilities), and the exclusion: 'to map one phrase to IDs use resolve_capabilities instead.' Both the when and the when-not are explicit with a named alternative.

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