Skip to main content
Glama

status

Report paths, game/bridge state and anything that needs fixing ("warnings"), and ping each in-game bridge.

Instructions

Report paths, game/bridge state and anything that needs fixing ("warnings"), and ping each in-game bridge.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that the tool pings each in-game bridge, which suggests a side effect or network/process interaction, and that it reports warnings. However, it does not describe permissions, timeout behavior, whether pings mutate state, or failure handling. The output schema reduces the need to explain return values, but behavioral disclosure remains incomplete.

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?

The description is a single front-loaded sentence with no filler. It is slightly dense, packing four reporting targets and a ping action together, but every clause contributes useful information.

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?

For a zero-parameter diagnostic tool with an output schema, the description covers the core scope: paths, game/bridge state, warnings, and bridge pings. It could be more complete by stating when to run it or what a warning implies, but nothing critical is missing for basic invocation.

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 has zero parameters, so there is no parameter semantics to obscure. Schema description coverage is 100%, and the empty input schema is consistent with the description.

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 uses a specific verb ("Report") and names concrete resources: paths, game/bridge state, warnings, and pinging in-game bridges. This clearly identifies a diagnostic status tool, though it does not explicitly contrast itself with siblings like setup or console_log.

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?

Usage is implied as a health/diagnostic check for paths, bridge state, and warnings, but there is no explicit when-to-use guidance, no when-not-to-use conditions, and no named alternatives.

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