Skip to main content
Glama

apply_knee_repair

Applies a still-current preview as an undoable action after rechecking its constraints, ensuring the change is valid before committing.

Instructions

Apply a still-current preview in an undoable Action variant after rechecking its constraints.

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": "apply_knee_repair"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNo
candidate_idYes
expected_sessionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3/5.0
Behavior4/5

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

The annotations only declare the generic profile (not read-only, not destructive, not idempotent, closed world). The description adds genuinely new behavior: the result is undoable, and constraints are re-validated at apply time so a stale preview will not silently commit. The failure mode and reversibility are exactly the kind of context annotations cannot express. It loses points for not saying whether the recheck failure is an error or a no-op.

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 sentence with the verb front-loaded, so nothing is wasted by length, but the density of unexplained jargon ("Action variant", "constraints") makes it opaque rather than efficient. Brevity here buys ambiguity rather than clarity.

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, but this is a state-mutating commit step with two required arguments at 0% schema coverage and no explicit relationship to preview/cancel siblings. An agent still lacks enough to construct a valid, first-try call.

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 three parameters (candidate_id, expected_session, timeout) are completely undocumented in the schema. The description mentions no parameter by name; "its constraints" only vaguely gestures at expected_session as a session guard, and candidate_id/timeout get no meaning at all.

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?

The verb is clear ("Apply") and the resource is a "preview", but the qualifiers ("still-current", "undoable Action variant") are internal jargon that blurs what is actually committed. An agent can infer this is the commit step of the preview/apply/cancel trio, but the description never states the subject matter (knee repair) or names a sibling for contrast.

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?

"still-current preview ... after rechecking its constraints" implies usage preconditions: a prior preview must exist and be non-stale. That is useful implicit routing to preview_knee_repair, but it is never stated explicitly, nor is when to prefer cancel_knee_repair or what happens on a stale candidate.

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