Skip to main content
Glama

get_capabilities

Read-only

Retrieves available renderers and explains why some are unavailable so agents can choose valid rendering options in the demoreel MCP server.

Instructions

Server capabilities: which renderers are available here and why not.

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral fact — that it explains why a renderer is unavailable, not just which ones exist — but it doesn't say whether results are static or environment-dependent.

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

Conciseness3/5

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

It is short, which is good, but the fragmentary phrasing and the dangling 'and why not' make it harder to parse than a single plain sentence would be. The useful information is there but buried in an awkward construction.

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?

With an output schema present and read-only annotations, the description doesn't need to explain return values, so the burden is light. Still, for a tool whose whole job is interpretation (availability and reasons), one more clause on what a negative result means would make it complete.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies.

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

Purpose3/5

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

The description says the tool reports server capabilities, specifically which renderers are available, which is a clear enough resource. But it is a sentence fragment ('Server capabilities: ...') that never states a verb or the tool's action, and 'which renderers are available here and why not' reads as a label rather than a stated purpose.

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

Usage Guidelines2/5

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

There is no statement of when to call this tool, whether it should be consulted before calling render_highlight or render_reel, or what it means if a renderer is unavailable. An agent must infer the use case entirely.

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