Skip to main content
Glama
Sign In
Slicewise

Slicewise

by gjlmotea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search for 3D models

bambu_search_models
Read-onlyIdempotent

Search 3D models across Thingiverse, MakerWorld, and Printables; get Thingiverse results or direct search links for MakerWorld and Printables. Does not download models.

Instructions

Searches for models across platforms. Thingiverse uses its official API (requires THINGIVERSE_TOKEN). MakerWorld and Printables have no official public API, so for them only a search link is returned for a person to open; this is a deliberate downgrade: no scraping or private endpoints pretending to be an API. Do not claim to have searched or downloaded models from those platforms. Does not download any model. Accesses the internet.

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": {
      "query": "<query>"
    },
    "name": "bambu_search_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
sourcesNoRestrict to these platforms; omit to query all. See catalogs in bambu_get_status for the available values.

Output Schema

NameRequiredDescriptionDefault
queryYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, openWorld, non-destructive), and the description adds substantive context on top: the THINGIVERSE_TOKEN auth requirement, the deliberate degradation for MakerWorld/Printables, and the no-scraping policy. That is exactly the kind of platform- and credential-level behavior an agent cannot infer from structured fields.

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

Conciseness3/5

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

Purpose is front-loaded, which is good, but several clauses are meta-commentary about implementation philosophy ("this is a deliberate downgrade: no scraping or private endpoints pretending to be an API") rather than operational facts. The agent-directed prohibition ("Do not claim to have searched") is useful once, but the passage reads longer than the three facts it conveys.

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?

Because an output schema exists, the description is not obligated to explain return values, and it still usefully warns that link-only results differ in kind from real search results. The remaining gap is operational: nothing tells the agent what `limit` controls or how to phrase `query` for best results.

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 only 33%, so the description has to carry weight; it names the three platforms, which gives the `sources` array concrete values even though the schema defers to bambu_get_status. However, `query` and `limit` (capped at 30) are never explained — no guidance on search syntax, result ordering, or default page size — leaving half the parameters undocumented in both places.

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?

States a specific verb and resource ("searches for models") and then scopes it per platform: Thingiverse via official API, MakerWorld/Printables returning only a search link. It also carves out the negative space ("Does not download any model"), which cleanly separates it from download/inspect siblings like bambu_inspect_model.

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 clear context on when results are real versus link-only, and an explicit warning not to claim it searched platforms where it only produced a link. It does not name an alternative sibling to use when a download or deeper model inspection is actually needed, so routing to alternatives is left implicit.

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