Skip to main content
Glama
formastep-mcp
by eldertek

view_render_svg

Idempotent

Render a deterministic Top/Front/Right orthographic SVG from a PartSpec or mesh to produce consistent 3-view drawings for review or manufacturing.

Instructions

Render a deterministic 3-view orthographic SVG (Top/Front/Right) from a PartSpec or mesh.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "view_render_svg"
  }
}

Input Schema

NameRequiredDescriptionDefault
specNo
mesh_pathNo
output_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior; "deterministic" usefully reinforces the idempotency guarantee. However, the description never says that a file is written (implied only by readOnlyHint=false and the output_path param), nor what happens on overwrite or how large meshes are handled. It adds some context but leaves the write behavior implicit.

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?

A single front-loaded sentence with no filler; the output format and view convention are stated before the input sources. Nothing could be trimmed without losing information.

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 no explanation, but the input side is the weak point: three optional, entirely undocumented parameters with an ambiguous relationship between spec and mesh_path. For a rendering tool where passing the wrong source silently yields nothing, the description should resolve that ambiguity.

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 all three parameters are optional with null defaults, so the description carries the full burden. It maps loosely onto spec and mesh_path via "PartSpec or mesh" but does not state precedence or exclusivity when both or neither are supplied, and output_path is never mentioned at all.

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?

Names a specific verb ("Render") and a precisely qualified resource ("deterministic 3-view orthographic SVG (Top/Front/Right)"), plus the two accepted input sources. An agent can distinguish this from part_build or step_inspect by the output artifact alone. It stops short of naming any sibling explicitly, so it is clear but not fully differentiated.

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?

"from a PartSpec or mesh" implies which inputs are acceptable and therefore when the tool applies, but there is no statement of when to prefer this over export_manufacturing_bundle or step_inspect, and no prerequisites. Usage must be inferred from the artifact described.

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