Skip to main content
Glama

Search 3D designs

search_designs
Read-onlyIdempotent

Search the public Printlooper marketplace of 3D-printable designs by keyword or category. Returns titles, sizes, images and the page where a buyer can order a print or a seller can add the design to their shop.

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

Input Schema

NameRequiredDescriptionDefault
sortNorecommended
limitNo
queryNoKeywords, for example "cable organizer" or "planter"
offsetNo
categoryNoA marketplace category, if the user named one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context beyond that: the catalog is public, and the result set carries titles, sizes, images and a page where either a buyer can order or a seller can add the design — the dual audience is a useful behavioral detail. Pagination and result-count behavior are still unstated.

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?

Two sentences, front-loaded with purpose and followed by return contents; nothing is redundant. The second sentence is slightly list-like but earns its space given there is no output schema.

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 five-parameter, zero-required search tool with no output schema, the description covers purpose and return shape adequately but leaves paging (offset/limit interaction, the 500-offset ceiling) and sort semantics entirely to an under-documented schema. An agent could call it, but not page or rank results confidently.

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 only 40%, and the description only echoes the two parameters already documented in the schema (query and category). Sort, limit and offset — including the hard caps of 20 per page and 500 offset — get no explanation in either place, so the description fails to compensate for the coverage gap.

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 (search) and a precisely scoped resource (the public Printlooper marketplace of 3D-printable designs) plus the two filter axes, keyword and category. An agent can distinguish it from a single-record fetch like get_design, but the description never names that alternative explicitly.

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?

Usage is only implied: search when the user has keywords or a category. There is no explicit when-to-use vs. when-not framing, no pointer to get_design for retrieving one known design, and no note that an empty query with sort/offset is a valid browse mode.

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