Skip to main content
Glama

Get a 3D design

get_design
Read-onlyIdempotent

Details of one public design from search_designs: description, size, tags, whether it needs hardware, and its page.

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": {
      "design_id": "<design_id>"
    },
    "name": "get_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world behavior, so the description's additions are the valuable part: it discloses that only *public* designs are returned and enumerates the payload fields (description, size, tags, hardware requirement, page). It does not say what happens for a missing or private design_id, which is the main remaining behavioral gap.

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 that names the resource, its source, and the return contents with no filler. Every clause carries information.

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

Completeness4/5

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

A simple annotated read tool with one parameter and no output schema; the description usefully summarizes return fields in place of an output schema. Only the error/not-found behavior for non-public or invalid IDs is left uncovered.

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 0%, so the single design_id parameter is undocumented in the schema and the description must compensate. It only hints that the ID comes from search_designs results, adding no format, length, or sourcing detail beyond that inference.

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 and resource ("Details of one public design") and enumerates the returned facets, which separates it from the sibling search_designs listing tool. The link to design_id is only implied through "from search_designs," so it falls just short of a fully self-contained purpose statement.

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?

The phrase "from search_designs" implies the intended sequence: search first, then fetch one design's details. There is no explicit when-not guidance, no statement about behavior for IDs that belong to non-public designs, and no mention of alternatives, so usage is implied rather than spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources