Skip to main content
Glama

backend_capabilities

Reports supported product versions and protocol feature availability by backend, with optional skill filtering and version classification into support tiers and per-feature breakdowns.

Instructions

Report supported product versions and protocol feature availability per backend. Optionally filter by skill and classify a specific backend version into its support tier with a per-feature availability breakdown.

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

Input Schema

NameRequiredDescriptionDefault
skillNoFilter to one skill id (e.g. "metrics", "logs", "traces").
backendNoBackend display name to classify (e.g. "Prometheus"). Requires skill + version.
versionNoDetected version to classify (e.g. "3.0.1"). Requires skill + backend.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. 'Report' implies a read-only operation and the description does disclose what comes back (supported versions, per-feature availability, support tier). It does not state what happens when backend/version are unknown, whether versions are normalized, or any permission/caching behavior, leaving meaningful gaps for an annotation-free tool.

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?

Two sentences, front-loaded with the primary purpose before the optional classification mode. No filler. The second sentence is dense but every clause (skill filter, backend version, support tier, per-feature breakdown) carries information.

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 no annotations and no output schema, the description must convey both behavior and return shape; it does so at a high level (tiers, per-feature availability). It does not clarify the base mode's inputs (is skill required to list versions?) or the failure behavior for unsupported versions, which matters for a three-parameter tool with all-optional parameters.

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 schema already documents each parameter including the 'Requires skill + version' dependency. The description only restates that 'skill' is an optional filter and that classification needs a backend version, adding little beyond the schema. Baseline 3 is appropriate.

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 gives a specific verb+resource ('Report supported product versions and protocol feature availability per backend') and adds a second mode ('classify a specific backend version into its support tier'). It is clearly a capability/version-discovery tool, distinguishable from the query-oriented siblings like metrics_query or logs_query. It stops short of naming a sibling it is meant to replace, so it lands at 4 rather than 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?

The two modes are described (filter by skill; classify a backend version), which implies when each parameter set applies. However, there is no explicit 'use this when…' statement and no exclusion or alternative tool named. An agent can infer usage but must reason about it rather than read it.

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