Skip to main content
Glama

workbench_handoff_to_craft

Persist an evidence-linked diagnosis and repair/test request into a Craft Anything investigation, preparing a coding-agent handoff to generate fixes and tests.

Instructions

Persist an evidence-linked diagnosis and repair/test request into the real Craft Anything investigation via core_handoff_write. This prepares the coding agent handoff; it does not secretly invoke a paid model or edit source. The host/Craft coding agent then generates the fix and tests.

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": {
      "case_id": "<case_id>",
      "finding_id": "<finding_id>"
    },
    "name": "workbench_handoff_to_craft"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idYes
finding_idYesID from workbench_record_finding. Diagnosis, verification level and evidence are inherited and revalidated.
constraintsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already indicate this is not read-only, is open-world, and is not destructive. The description adds useful behavioral context: it persists into the real Craft investigation, does not secretly invoke a paid model, and does not edit source, with the host coding agent generating fixes and tests afterward.

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?

The description is three tight sentences with the core action front-loaded. The clarification about not invoking a paid model or editing source earns its place by defining the handoff boundary.

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

Completeness3/5

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

The description covers the purpose and the handoff workflow, and it clarifies key non-actions. It remains incomplete for a write-oriented, open-world tool with no output schema and low parameter coverage: it does not explain case_id or constraints, nor what persistence result the caller should expect.

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 only 33%, and the description adds no parameter-level meaning for case_id or constraints. The schema itself documents finding_id well, including inheritance and revalidation of diagnosis, verification level, and evidence, but the description does not compensate for the undocumented parameters.

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?

The description uses a specific verb and resource: persisting an evidence-linked diagnosis and repair/test request into the real Craft Anything investigation via core_handoff_write. It also distinguishes the action from secret model invocation and source editing, making the intended handoff role clear.

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?

The workflow is implied: this prepares the coding agent handoff, after which the host/Craft coding agent generates the fix and tests. However, there is no explicit guidance about when to call this instead of siblings such as workbench_record_finding or workbench_close_case.

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