Skip to main content
Glama

List capabilities

list_capabilities
Read-onlyIdempotent

Discover caller-authorized scientific tools and their exact released operation readiness and input requirements.

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
tagsNoRequire every supplied capability tag.
limitNo
queryNoCase-insensitive text matched against ID, tool, name, description, and tags.
cursorNo
statusNoavailable
tool_idNoExact native tool identifier filter.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 openWorldHint=false, so the safety profile is covered. The description usefully adds that results are permission-filtered ("caller-authorized") and carry operation readiness, but it omits the important default behavior that status defaults to "available" (hiding unavailable capabilities) and says nothing about 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 with no filler. It is efficient, but stacks several abstract qualifiers ("exact released operation readiness") that could have been spent on more actionable detail.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and annotations cover the safety profile. For a 6-parameter filtered list tool, however, the description leaves out the default availability filtering and pagination semantics that materially affect how an agent queries it.

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

Parameters2/5

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

Schema coverage is only 50%: tags, query and tool_id are documented in the schema, but limit, cursor and status are not. The description alludes indirectly to status ("operation readiness") but adds no meaning for the pagination parameters or for how tags/query combine, so it does not compensate for the coverage gap.

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?

"Discover caller-authorized scientific tools and their exact released operation readiness and input requirements" gives a specific verb (discover) and resource (scientific tools/capabilities) plus the scope qualifier that results are limited to what the caller is authorized to see. It is clear enough to distinguish browsing from the get_capability / run_capability siblings, though it never names them and the phrase "exact released operation readiness" is jargon-heavy.

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?

Usage is only implied: "discover" suggests a browse-before-run step, and "caller-authorized" hints at permission-scoped results, but the description never states when to use this versus get_capability (single lookup) or search_catalog. No explicit exclusions or alternatives are given.

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