Skip to main content
Glama

get_design_template_info

Read-only

Retrieve a design template by ID from either library and identify its type. Parametric parts return parameters, defaults, and units for generation; design patterns return use cases and print guidance.

Instructions

Look up one design template by id — parametric part or pattern.

        Resolves an id from EITHER library and says which it came
        from, so a caller never has to know in advance:

        * a PARAMETRIC PART (``generatable: true``) comes back with
          its full parameter list — names, defaults, and units — which
          is what you need to fill in the user's own dimensions and
          call ``generate_from_template``.
        * a DESIGN PATTERN (``generatable: false``) comes back with
          its use cases, material compatibility, and print
          orientation.  Patterns are guidance for OpenSCAD you write
          yourself; ``generate_from_template`` does not accept them.

        Args:
            template: Template identifier, from either library —
                e.g. "shelf_bracket" (part) or "snap_fit_cantilever"
                (pattern).  Use ``find_design_templates`` to search.
        

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": {
      "template": "<template>"
    },
    "name": "get_design_template_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateYesTemplate identifier, from either library — e.g. "shelf_bracket" (part) or "snap_fit_cantilever" (pattern). Use ``find_design_templates`` to search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / template / description
      Added value: +"Template identifier, from either library — e.g. \"shelf_bracket\" (part) or \"snap_fit_cantilever\" (pattern).  Use ``find_design_templates`` to search."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only annotations, it explains that the same id may resolve from either library, reports which library it came from, and describes different return content for generatable parts versus patterns. This is useful behavioral context not supplied by the annotations.

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?

The description is front-loaded and well structured, with useful bullets separating parts from patterns. The Args section duplicates the schema description, which is slightly redundant but not harmful.

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?

For a read-only lookup with no output schema, the description explains what each template kind returns and how the result should be used. An agent has enough information to call this correctly and route the outcome to generate_from_template when appropriate.

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

Parameters3/5

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

Schema coverage is 100%, and the description largely repeats the schema's examples and guidance for the single template parameter. It reinforces that ids may come from either library, but adds little syntax or meaning beyond the schema.

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 states a specific verb and resource: 'Look up one design template by id.' It also distinguishes two template kinds and names related tools, so an agent can tell this apart from generate_from_template and find_design_templates.

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

Usage Guidelines5/5

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

It gives explicit routing guidance: use find_design_templates to search, use this tool to resolve an id from either library, and use generate_from_template only for parametric parts. It also clearly excludes design patterns from generate_from_template.

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