Skip to main content
Glama

faultydata

start_battery

Mint a report-card battery token. The client then runs /run/{token}/{id} per specimen and reports outcomes.

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

Input Schema

NameRequiredDescriptionDefault
clientNoClient label, e.g. httpx/0.28

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the key downstream mechanism (the token is embedded in a /run/ URL path). However, it omits token lifetime/expiry, whether minting creates server-side state, whether repeated calls invalidate prior tokens, and any auth requirements — significant gaps for a token-issuing operation.

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 waste, and the core action is front-loaded ahead of the downstream usage note. Nothing is padded or repeated.

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 one-optional-parameter tool with no output schema, the description conveys what is produced (a token) and how it is consumed, which is the essential contract. Missing token lifecycle details keep it from being fully complete, but an agent can call it correctly from this text.

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 coverage is 100% and the single `client` parameter is optional and fully documented in the schema as a client label. The description never mentions `client`, so it adds no meaning beyond the schema; baseline 3 applies.

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 ('Mint') with a specific resource ('report-card battery token'), so the agent knows this creates a token rather than reading reports or specimens. It doesn't explicitly contrast with siblings like get_report or list_specimens, but the action is distinct enough to disambiguate.

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?

It gives real workflow guidance: mint the token first, then the client calls /run/{token}/{id} per specimen and reports outcomes. That tells the agent where this tool sits in the sequence. It stops short of stating exclusions (e.g., whether a token should be reused across batteries or re-minted per run).

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