Skip to main content
Glama

Stop a check

cancel_check
DestructiveIdempotent

Stop further paid steps of a check. Work already sent can finish and is charged; saved results stay. Does not pause the alert.

Permission: work:execute.

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": {
      "check_id": "<check_id>"
    },
    "name": "cancel_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
check_idYesThe check ID returned when it was quoted or created.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description nonetheless adds real value beyond them: in-flight work completes and is billed, saved results persist, the alert is unaffected, and a work:execute permission is required — this is exactly the partial-destruction and cost semantics an agent needs. It stops short of saying what happens when the check is already finished or cancelled.

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?

Three tight sentences: the action first, then the completion/billing consequences, then the alert exclusion and permission. Every clause carries distinct information with no repetition of the title or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive single-parameter mutation with an output schema and full annotation coverage, nothing an agent needs is missing: action, side effects, retained state, permissions, and the explicit boundary that the alert is not paused.

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?

There is a single parameter at 100% schema description coverage, with the schema already explaining the check_id as the ID returned at quote or creation time. The description adds nothing further about the parameter, so 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?

States a specific verb and resource: 'Stop further paid steps of a check.' The scoping phrase 'further paid steps' and 'check' implicitly distinguish it from cancel_preview, approve_check, and list_results, though no sibling is named explicitly.

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 rather than stated: an agent can infer it is for halting an in-flight check, and 'Does not pause the alert' rules out a look-alike intent. There is no explicit guidance on when to prefer cancel_preview or when cancellation is inappropriate (e.g. after completion).

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