Skip to main content
Glama

body_status

Report real capability states—importable, launched, blocked, or not configured—and verify before claiming support, so agents act on confirmed status, not assumptions.

Instructions

Real capability states: what is importable, launched, blocked, or not configured — never claimed as 'verified' without a real check.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/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 behavioral burden. It does add one genuinely useful disclosure: the states are derived from real checks, never asserted as 'verified' without one — this tells the agent the output is trustworthy rather than cached or optimistic. It stops short of saying whether the call is cheap, side-effect free, or slow, which matters for a zero-arg probe.

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?

A single sentence with no filler, and the state vocabulary is front-loaded. The phrasing is slightly awkward ('Real capability states:' as a fragment) and would be tighter with an explicit verb such as 'Reports'.

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?

For a zero-parameter status tool with no output schema, the description should carry the entire burden of explaining what comes back, and it only partially does so by listing four possible states. It does not indicate whether results cover models, consoles, tasks, or all of them, nor whether anything is scoped per-workspace or profile.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The enumerated state names are a bonus that helps the agent interpret results rather than inputs.

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 names the resource implicitly (capability states) and enumerates the state vocabulary: importable, launched, blocked, not configured. However, it never says what the tool actually returns or does — whether it's a diagnostic report, a readiness check, or a list of subsystems. An agent can guess it's a status read, but cannot distinguish it confidently from body_task_status or body_models.

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 when-to-use guidance, no prerequisites, and no named alternative. The sibling set contains several status-like tools (body_task_status, body_models, body_local_models), and the description does nothing to route between them.

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