Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Get model details

get_model
Read-only

Retrieve complete details for a specific CAD model using its ID, including downloadable files, metadata, licence, tags, accuracy scores, and datasheet counts.

Instructions

Full details for one model: files (with file_id for downloading), size, licence and attribution, tags, creator, company, source, score summary, comment and datasheet counts. Description, README and licence text are under user_content. Doesn't count as a page view.

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

Input Schema

NameRequiredDescriptionDefault
model_idYesThe model's id (uuid) from search results or its page URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the description isn't needed for the safety profile. It still earns credit by disclosing two traits the annotations do not: the call does not register a page view, and the heavy text fields (description, README, licence) are segregated under user_content, while file_id is the handle for a subsequent download. That is genuine behavioral context that shapes how an agent consumes the response.

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 the resource and its payload, and the return-field enumeration is dense but each item tells the agent something it can act on. The only mild cost is the crammed parenthetical around files/file_id, but nothing is wasted or redundant.

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?

With no output schema, the description must describe return values and it does so thoroughly, including where the bulky text lives. The remaining gap is volume and pagination characteristics of the files list, which an agent might want before calling, but for a single-record read tool this is close to complete.

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?

There is a single parameter, and the schema already documents model_id at 100% coverage, including where to obtain it (search results or page URL). The description adds nothing about the identifier itself, so the baseline of 3 applies when the schema carries the full burden.

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 ('Full details for one model') and then enumerates exactly what comes back: files with file_id, size, licence/attribution, tags, creator, company, source, score summary, comment and datasheet counts. This is distinguishable from the search_models sibling at a glance because it is scoped to a single model and returns the complete record rather than a result list.

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: an agent can infer this is the follow-up call to search_models for detail on a chosen model, and the 'Doesn't count as a page view' note gives a mild incentive to use it. There is no explicit when-to-use versus when-not statement and no named alternative, so guidance is adequate but not directive.

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