Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Download a file

download_file

Downloads a model's CAD file to your computer, returning the saved path, licence, and attribution; check download availability first to confirm daily download credits.

Instructions

Download one of a model's files to this computer. The first file of a model each UTC day uses one of the user's CommunityCAD downloads; more files of that model the same day and repeats are free (call check_download first). Returns the saved path, the licence and the attribution line.

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

Input Schema

NameRequiredDescriptionDefault
file_idNofile_id from get_model. Optional when the model has one file.
model_idYes
directoryNoSave here instead of ~/CommunityCAD/<model-slug>/.
zip_memberNoFor a ZIP file: also extract this one member (path or file name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare a non-read-only, open-world, non-idempotent but non-destructive write; the description adds real context beyond that: the per-UTC-day quota accounting, that repeats are free, and that the call returns the saved path, licence and attribution line. It does not mention file size limits, overwrite behavior when the target path exists, or what a quota failure looks like, keeping it below top marks.

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?

Three sentences, front-loaded with the action, then quota rules, then return values — a sensible ordering with no filler. The quota sentence is slightly dense ('more files of that model the same day and repeats are free') but 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?

With no output schema, the description usefully discloses the return payload (saved path, licence, attribution) and the quota mechanics an agent cannot infer from annotations. Four parameters are mostly covered by the schema, so the definition is close to complete for a download tool; overwrite/collision behavior is the notable omission.

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 75%, with file_id, directory and zip_member already documented inline, so the description is not required to carry parameter meaning. It adds no further syntax or defaults of its own beyond implying the file is saved locally, so baseline applies.

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 ('Download one of a model's files to this computer') and scopes the action to a local destination, which cleanly separates it from siblings like get_model, show_images or upload_model. An agent can identify the operation without opening the schema.

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?

Provides an explicit prerequisite — 'call check_download first' — and explains the daily quota condition that governs whether a download costs anything, which effectively tells the agent when this call is free versus charged. It stops short of naming when-not-to-use or an alternative download path, but the routing guidance is clear.

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