Skip to main content
Glama
Sign In
mcp-spatial-critic

mcp-spatial-critic

by vanovri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_presets

Lists bundled parametric CAD presets for OpenSCAD generators, letting agents choose a starting model instead of defining geometry from scratch.

Instructions

List the bundled parametric CAD presets (OpenSCAD / generator).

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_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. "List" implies a safe read, and "bundled" discloses that only built-in presets are returned, but the description says nothing about what a preset contains, ordering, or whether the list is static or generator-derived.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with the resource front-loaded and no wasted words. The "(OpenSCAD / generator)" aside is terse to the point of being slightly cryptic, but it does add source context rather than filler.

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?

For a zero-parameter list tool with no output schema, the agent still needs to know roughly what comes back (preset names, identifiers, or parameters) in order to act on the result. The description establishes the domain but not the shape or use of the returned presets, leaving a modest gap.

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 no parameter semantics to explain; the baseline for a no-arg tool applies. The description does not need to compensate for anything here.

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?

States a specific verb ("List") and resource ("bundled parametric CAD presets"), with a parenthetical naming the source domain (OpenSCAD / generator). It is clearly distinct from siblings like audit_stl and generate_reference_box, though the description never explicitly says so; differentiation comes from the resource itself rather than deliberate contrast.

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?

"Bundled" implies these are built-in presets rather than user-defined ones, which narrows the expected context, and listing presets before a generate call is the obvious use. However, there is no explicit when-to-use statement, no mention of the generator sibling as the consumer of these presets, and no exclusions.

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

Deploy Server

Other Tools