forge3d-mcp

Create Handoff

create_handoff

Generates a JSON and Markdown handoff packet capturing specs, artifacts, owners, and next steps so the next agent or teammate can continue without prior context.

Instructions

Write a handoff packet (JSON + Markdown) so the next agent or teammate needs no context.

owners maps a role to a name, e.g. {"design": "priya", "geometry": "agent-a"}.

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": {
      "spec": "<spec>"
    },
    "name": "create_handoff"
  }
}

Input Schema

Name	Required	Description	Default
`spec`	Yes
`notes`	No
`checks`	No
`owners`	No
`backend`	No
`out_path`	No
`artifacts`	No
`next_agent`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.7Nov 4, 2026

TDQS

B3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure and does not meet it. It never states whether a file is written to disk, whether an existing packet at out_path is overwritten, what backend selects, or that a required spec must already exist — all material for a tool that produces persisted artifacts.

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?

Two tight sentences with the purpose front-loaded and the parameter example attached to the field it clarifies. Nothing is padded or redundant.

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?

For an 8-parameter tool with nested objects, a required spec, and zero annotation coverage, the description accounts for one parameter and no side effects. The existence of an output schema covers the return-value side, but the input and behavioral story is largely missing.

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% across 8 parameters, so the description must compensate, and it explains only one of them (owners, with a helpful role-to-name example). spec, notes, checks, artifacts, backend, out_path, and next_agent are left entirely undefined in both the schema and the prose.

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?

The description gives a specific verb and resource ("Write a handoff packet") plus the concrete output form (JSON + Markdown) and the goal (next agent needs no context). That is enough to distinguish it from every sibling, which are all model/scene/job operations rather than handoff authoring, but it does not explicitly name that separation.

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 only implied by the stated goal — you use it when work must be handed to another agent or teammate without re-explaining context. There is no explicit when-to-use trigger, no prerequisites, and no guidance on how it relates to siblings such as checklist or model_card, which could plausibly overlap in capturing state.

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