Skip to main content
Glama
com.woodstitch/tts-human-eval

com.woodstitch/tts-human-eval

Official

woodstitch_cancel_eval

Destructive

Stop a TTS human evaluation early with confirmation; only work already handed to listeners is charged, and in-progress tasks finish and are paid.

Instructions

Stop an evaluation early. Charges only for work already handed to listeners; anyone mid-task finishes and is paid. Check max_additional_charge_if_canceled_now_usd via woodstitch_get_eval first if the user wants that number. Requires confirm=true.

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": {
      "eval_id": "<eval_id>"
    },
    "name": "woodstitch_cancel_eval"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
eval_idYes
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description goes further by explaining the billing model: charges apply only to work already handed to listeners, and in-flight tasks finish and are paid. That is exactly the cost/irreversibility context an agent needs before a destructive call. It omits what happens if confirm is false and how idempotency_key behaves, keeping it short of a 5.

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?

Three short sentences with the core action front-loaded, followed by cost implications and the prerequisite. The get_eval pointer is slightly lumped together with pricing vocabulary, but no sentence is wasted.

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 destructive, billing-relevant mutation with no output schema and zero schema description coverage, the description covers the cost outcome and the confirmation gate, which is the bulk of what matters. The remaining gap is the idempotency_key semantics and the failure behavior when confirm is not set.

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 0%, so the description must carry parameter meaning itself. It explains the confirm=true requirement, which is the non-obvious gate on this call, and eval_id is self-evident from the name, but idempotency_key is never mentioned in either schema or description, leaving one of three parameters undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Stop an evaluation early') that is immediately distinguishable from the sibling lifecycle tools start_eval, get_eval, and list_evals. An agent knows exactly what action this performs without opening the schema.

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?

Gives a clear condition for consulting woodstitch_get_eval first ('if the user wants that number') and states the confirm=true prerequisite, which routes the agent correctly before invoking. It stops short of naming explicit when-not-to-cancel conditions or alternatives beyond the pricing check, so it is strong but not exhaustive.

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