forge3d-mcp

List Shapes

list_shapes

Browse maths-defined 3D shapes with equations, parameters, and print-safe solid vs. visual-only surface notes so you can choose a shape family before creating geometry.

Instructions

Catalogue of maths-defined shapes, with the equation and parameters for each.

Call this before create_shape. Every entry states whether it is a closed solid (safe to print) or an open surface (visual only), and what each parameter does — so you can pick a family instead of writing vertex loops.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.7Nov 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations present, the description does real work: it discloses that entries are labelled closed solid (safe to print) vs open surface (visual only), which is a downstream-consequence distinction an agent could not infer elsewhere. It does not discuss limits, freshness, or ordering of the catalogue, so a small gap remains.

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?

Three short sentences, front-loaded with what the tool returns, then the sequencing instruction, then the reason the sequencing matters. The 'vertex loops' phrasing is the only flourish and it justifies the tool's existence.

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

Completeness5/5

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

An output schema exists, so the description need not enumerate return fields; instead it supplies the one piece of interpretation an agent needs — the closed vs open classification and the per-parameter explanations. For a zero-parameter read tool this is complete.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema already conveys. Baseline of 4 applies; there is no parameter-level meaning left unstated.

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?

Names a specific resource (a catalogue of maths-defined shapes) and states exactly what each entry contains — the equation and its parameters. An agent can distinguish this from create_shape without opening either schema, since this one retrieves definitions rather than producing geometry.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit sequencing guidance — 'Call this before `create_shape`' — and frames the purpose as picking a family rather than writing vertex loops. It does not name conditions under which to skip it or point at any sibling other than create_shape, which keeps it short of a full when/when-not treatment.

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