Skip to main content
Glama

Check what this key may do

get_capabilities
Read-onlyIdempotent

Reports what this API key may do, without running anything: the analyses it is licensed for (analyze_vt, analyze_eov, analyze_substrate), the threshold models it can reach, the metrics compute_metrics may compute for it, its upload limits and the data-retention policy.

Meant as the first call of a session. The products are licensed separately, so a key with thresholds does not necessarily include oscillation analysis, and this answers that before any analysis is tried. Every operation it lists is run by its own tool, never by this one.

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 cover safety (readOnly, idempotent, non-destructive, closed-world), so the description rightly spends its words elsewhere, chiefly "without running anything" and the licence-granularity caveat that no annotation conveys. It does not pin down the response shape beyond listing the categories of information returned, which is the one remaining gap.

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?

Two short blocks: what it reports, then when to use it. The parenthetical tool list is compact and informative rather than padding, and no sentence merely restates the title.

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 and no parameters, the description carries the burden of describing returns, and it does so by enumerating the categories of capability reported. Slightly incomplete because the concrete field/format of the response is left unspecified, which mildly matters for a discovery call whose output drives later tool selection.

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 zero parameters, so there is no parameter meaning for the description to add; schema coverage is effectively complete. Baseline of 4 applies for a no-argument tool.

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 ("reports what this API key may do") and then enumerates the concrete content: licensed analyses, reachable threshold models, computable metrics, upload limits, retention policy. It also explicitly separates itself from siblings with "Every operation it lists is run by its own tool, never by this one," so an agent will not mistake it for analyze_vt or compute_metrics.

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 ordering instruction ("Meant as the first call of a session") plus the reason a call is needed: products are licensed separately, so a key with thresholds may lack oscillation analysis. That tells the agent both when to call it and why a failed/absent capability is expected rather than an error to retry.

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