Skip to main content
Glama

Check an accusation

check_accusation

Checks a formal accusation in a Plot Speaks mystery. Returns the verdict line for the accused person, starting Correct. or Innocent., and the name it matched. Records the accusation and verdict anonymously. Call it silently: never say "let me check", "let me check on that", "one moment" or "hang on" before or after, and never mention the tool.

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": {
      "slug": "<slug>",
      "accused": "<accused>"
    },
    "name": "check_accusation"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe story slug
accusedYesThe name of the person the user accused
play_idNoThe play id from start_story

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses the side effect ("Records the accusation and verdict anonymously"), the return contract (verdict line prefix plus matched name), and an interaction constraint (call silently, never narrate the check). The "records" claim is consistent with readOnlyHint=false, so there is no contradiction, and the disclosure meaningfully exceeds what the annotations convey.

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 purpose is front-loaded in the first sentence and the return format follows immediately. The enumerated forbidden filler phrases are somewhat repetitive, but each is a deliberate behavioral rule rather than padding, so the length is largely earned.

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?

With no output schema, the description correctly carries the return-value burden by describing the verdict line and matched name, and it explains the anonymized recording side effect for a non-read-only tool. The one real gap is what happens when the accused name matches nobody, which an agent would need in order to handle a miss correctly.

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 100%, so slug, accused, and play_id are already documented in the schema, which sets the baseline at 3. The description adds a small amount of meaning by calling the result "the name it matched," hinting that accused is matched fuzzily rather than compared exactly, but it offers no syntax, format, or fallback behavior for that parameter.

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 and resource ("Checks a formal accusation in a Plot Speaks mystery") and states what comes back ("the verdict line ... starting Correct. or Innocent., and the name it matched"). It does not name or contrast any sibling such as reveal_solution, so it stops short of the top mark, but an agent can identify the operation unambiguously.

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?

Usage context is clear from "a formal accusation" and the calling protocol is unusually explicit ("Call it silently: never say 'let me check'..."). There are no stated exclusions or alternatives — it never says what to do when the user merely speculates rather than formally accuses, or how this relates to reveal_solution — so it is clear context without the when-not guidance a 5 requires.

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