Skip to main content
Glama

Get capability

get_capability
Read-onlyIdempotent

Inspect one caller-authorized scientific operation, including its input contract and availability.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "capability_id": "<capability_id>"
    },
    "name": "get_capability"
  }
}

Input Schema

NameRequiredDescriptionDefault
capability_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real value on top: it discloses that results are scoped to the caller's authorization and that availability information is included. It stops short of saying what happens when the capability does not exist or is unauthorized (error vs empty result).

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?

One short sentence with zero filler, front-loaded with the verb and resource, then the two pieces of returned information. Nothing needs to be cut and nothing is buried.

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, return-value explanation is not required, and for a one-parameter read-only tool the description is close to sufficient. The remaining gap is that the core concept ('capability' / 'caller-authorized scientific operation') and the provenance of capability_id are never grounded, which matters for an agent seeing the term for the first time.

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 0%, so the single capability_id parameter is undocumented in structured data. The description only implies that the id selects 'one' operation and that authorization filters the namespace; it does not say where ids come from (presumably list_capabilities) or what form they take, so it only partially compensates 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?

The description pairs a specific verb ('Inspect') with a specific resource ('one caller-authorized scientific operation') and names what the response covers (input contract and availability). It is clear what the tool returns, but it never names the sibling it contrasts with (e.g. list_capabilities for enumeration vs run_capability for execution), so differentiation is left implicit.

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?

'Inspect one' implies single-item retrieval as opposed to listing, which gives some implied guidance, but there is no explicit when-to-use or when-not-to-use statement. In particular, nothing tells the agent whether this must be called before run_capability to learn the input contract, which is the most likely decision point.

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