Skip to main content
Glama

faultydata

get_report

Score a battery session and return the report card.

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": {
      "token": "<token>"
    },
    "name": "get_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesBattery token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/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. "Score" implies computation that may write or finalize session state, but the description does not say whether the call is idempotent, whether repeated scoring is safe, whether it fails on an incomplete session, or what the report card contains. Only the bare outcome is disclosed.

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?

One short sentence with the action and the return value front-loaded and no filler. It is efficient, though the brevity costs it the prerequisite and safety context a caller needs.

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 one-parameter tool with no output schema, the definition is close to minimally viable: it says it produces a report card but not its shape, and leaves preconditions for scoring unstated. The low complexity keeps the gap from being severe, but an agent could still invoke it at the wrong point in the session lifecycle.

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 token parameter is documented in the schema, so the baseline is 3. The description adds nothing about token provenance or format beyond restating that it identifies a battery.

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 ("score") with a specific resource ("battery session") and states the outcome ("return the report card"). That distinguishes it in practice from siblings like start_battery or replay_instructions, though it never names an alternative explicitly.

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 guidance on when to call this versus start_battery or replay_instructions, and no stated prerequisite such as whether the battery session must already be completed. The agent must infer the workflow ordering entirely from sibling names.

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