Skip to main content
Glama

Capabilities and the listings for each

list_capabilities
Read-onlyIdempotent

Every capability the directory tracks (web.search, inference.llm, data.company, …) with the best listings for each.

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": "list_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoListings per capability, best first (default 5)
prefixNoOnly capabilities whose id starts with this, e.g. web. or data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Listings per capability, best first (default 5)",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered elsewhere. The description adds only that listings are chosen as 'best' for each capability, which the schema also states via 'best first'. Nothing is said about result volume, ranking criteria, or pagination.

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?

A single front-loaded sentence that states the returned resource first and the per-capability payload second. No wasted wording; it would only improve by adding a routing clause to a sibling tool.

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 still conveys the return shape: a capability-to-listings mapping ranked best-first. For a two-optional-parameter read tool whose annotations are complete, that is close to sufficient, though it never hints at how many capabilities to expect or whether the output is large.

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 description coverage is 100%, so both limit and prefix are already fully documented with defaults and bounds. The description's id examples hint at prefix syntax but add nothing about either parameter. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose4/5

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

The description names the resource precisely: every capability the directory tracks, each paired with its best listings. The parenthetical examples (web.search, inference.llm, data.company) make the shape of a capability id concrete. It does not explicitly contrast itself with search_tools or get_tool, so it falls short of a 5.

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

Usage Guidelines3/5

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

Use is only implied by the phrasing: this reads as a taxonomy overview to browse before drilling in, but the description never says when to prefer it over search_tools or get_tool. There are no stated exclusions or prerequisites, so an agent must infer the routing.

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