Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Find similar models

find_similar
Read-only

Retrieve public 3D models similar to a specified model ID, ordered closest first. Use it to find comparable parts and alternatives when a model has been analyzed.

Instructions

Public models most similar to this one, closest first. Empty when the model hasn't been analysed yet.

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": {
      "model_id": "<model_id>"
    },
    "name": "find_similar"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
model_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value beyond that: results are pre-sorted by descending similarity and the call can legitimately return an empty set for unanalysed models, which prevents an agent from mistaking an empty list for failure.

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 short sentences, zero filler, with the core result and ordering front-loaded before the edge case. The second sentence is clipped to the point of being slightly telegraphic but still clear.

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 simple two-parameter read tool with annotations and no output schema, the description covers the essentials. It stops short of saying what the returned models look like or that limit caps the result count, which a careful agent would want.

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 description coverage is 0% across two parameters, so the description should compensate. 'This one' hints that model_id is the reference model, but the limit parameter (default 10, max 25) is never mentioned, leaving the agent dependent on raw schema metadata for half the inputs.

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?

The description names a specific resource (public models similar to a given one) and states the ordering, 'closest first', which an agent can act on. It is distinguishable from search_models in spirit (similarity vs. search), though it never explicitly contrasts the two.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and no alternative is named. The only conditional statement ('Empty when the model hasn't been analysed yet') describes an output edge case rather than steering tool selection.

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