Skip to main content
Glama

Get capabilities

get_capabilities
Read-onlyIdempotent

What Car Rental Brain measures, how fresh it is, and which airports/countries are covered. Use first when unsure whether a place is covered.

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
detailNoshort (default): the answer, with more_detail naming anything left out; full: every field.

Output Schema

NameRequiredDescriptionDefault
noteNo
errorNo
toolsNo
countriesNo
airports_measuredNo
latest_measurementNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "short (default): the answer, with more_detail naming anything left out; full: every field.",
      +  "enum": [
      +    "short",
      +    "full"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and a closed-world scope, so the safety profile is covered upstream. The description adds genuinely useful behavioral context — that the response reports measurement scope and data freshness — but says nothing about response shape, size, or what happens for uncovered places beyond a hint that something may be "left out".

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 sentences, zero filler: the first front-loads what the tool returns, the second immediately supplies the usage trigger. Nothing could be removed without losing routing value.

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 annotations, a fully documented parameter, and an output schema covering return values, the description's burden is light and mostly met. The one residual gap is what to do after coverage is confirmed — i.e., which sibling to call next.

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% and the single enum parameter is fully self-documenting, so the baseline of 3 applies. The description never mentions the detail control or the short/full trade-off, adding no meaning beyond the schema.

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 states concretely what the tool returns: the scope of the data (what is measured), its freshness, and geographic coverage by airport and country. That distinguishes it as a metadata/capability probe rather than a data-returning tool like airport_costs or list_airports, though it never explicitly contrasts itself with those siblings.

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

Usage Guidelines4/5

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

"Use first when unsure whether a place is covered" is an explicit routing rule with a clear triggering condition, which is exactly the decision an agent needs to make. It stops short of naming the alternative to call once coverage is confirmed, and gives no when-not-to-use case.

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.