mcp-sing

Overview Schema Source Related Servers Discussions Admin

compile_toolpath

Compile a deterministic toolpath for a handwritten signature, specifying pen type (fineliner or ballpoint), to enable reproducible plotting on a NextDraw 8511 pen plotter.

Instructions

Compila o toolpath NOMINAL (pré-calibração) para o proof. pen: fineliner|ballpoint.

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": {
      "signature_id": "<signature_id>"
    },
    "name": "compile_toolpath"
  }
}

Input Schema

Name	Required	Description	Default
`pen`	No		fineliner
`signature_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1Jul 4, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It mentions 'NOMINAL' and 'pre-calibration' but discloses no behavioral traits such as side effects, required permissions, or output format. The agent cannot infer safety or effects from this alone.

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?

The description is concise at one sentence, but it is slightly under-specified. It includes pen options inline but lacks structure like separate sections. It is not verbose, but could better front-load essential details.

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?

Given the tool's simplicity (two params, no output schema), the description is incomplete. It omits explanation of the essential 'signature_id' parameter and any prerequisites or workflow context, such as the proof stage. More context is needed for effective use.

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

Parameters1/5

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

Schema coverage is 0%, so description must add meaning. It only lists possible pen values but does not explain the role of 'signature_id' or how 'pen' affects compilation. No additional semantics beyond the schema are provided.

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 clearly states the tool compiles the NOMINAL toolpath for pre-calibration proof, specifying the verb 'compile' and resource 'toolpath NOMINAL'. It implicitly distinguishes from the sibling 'compile_calibrated' by noting pre-calibration, providing specific purpose and scope.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives like compile_calibrated. It only implies usage for proof and pre-calibration, but lacks clear when-not or context-based recommendations.

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