Skip to main content
Glama

cancel_knee_repair

Discard a live knee repair preview for a specified candidate and expected session, preventing stale or mismatched previews from being applied.

Instructions

Discard a live knee preview.

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": {
      "candidate_id": "<candidate_id>",
      "expected_session": "<expected_session>"
    },
    "name": "cancel_knee_repair"
  }
}

Input Schema

NameRequiredDescriptionDefault
candidate_idYes
expected_sessionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the safety profile is partly covered; the description adds only that the target is an ephemeral preview. It does not say what is lost by discarding (pending deformation edits?), what happens on a stale or already-cancelled session, or why the operation is not idempotent — all material for a mutating tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One six-word sentence with no filler, which is good, but the brevity is achieved by omission rather than discipline — for a two-parameter state-mutating tool this is under-specification, not conciseness.

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

Completeness2/5

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

An output schema exists so return values need not be described, which lowers the bar. Even so, a non-idempotent mutation with two undocumented required parameters and no mention of the preview workflow it belongs to is not complete enough for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and both parameters are required, so the description carries the full burden. It says nothing about candidate_id (presumably the preview handle) or expected_session (presumably a concurrency/optimistic-lock token), leaving an agent unable to know what values to supply or where to obtain them.

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

Purpose3/5

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

"Discard a live knee preview" gives a verb (discard) and an object (knee preview), so the general intent is inferable. But it never uses the word cancel/abort and never ties itself to the sibling preview_knee_repair / apply_knee_repair pair, so an agent must guess that this is the teardown step of the preview→apply workflow.

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 statement of when to call this versus applying the repair or simply letting the preview lapse, and no prerequisites (e.g. that a live preview session must exist). The only implicit cue is the adjective "live", which does not constitute usage guidance.

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