Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Upload a model

upload_model

Publishes a CAD model to CommunityCAD as public or private after user confirmation, with pictures, README and optional datasheets; blocks missing docs and returns the page link.

Instructions

Upload a new model to CommunityCAD (public or private) from a file or folder, with pictures, README and optional datasheets. Only after the user explicitly said yes and chose the visibility, the licence (for public) and whether it's 18+. Nothing is uploaded when documentation is missing. Same moderation as the website. Returns the page link.

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": {
      "path": "<path>",
      "title": "<title>",
      "description": "<description>",
      "readme_markdown": "<readme_markdown>",
      "visibility": "<visibility>",
      "is_mature": "<is_mature>",
      "image_paths": "<image_paths>"
    },
    "name": "upload_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe CAD file, or a folder to upload as a ZIP (hidden files, .venv, node_modules and __pycache__ are left out).
tagsNo
titleYes
licenseNoSPDX id the user chose, required for public: MIT, Apache-2.0, GPL-3.0, BSD-3-Clause, CC-BY-4.0, CC-BY-SA-4.0, CC0-1.0.
sourcingNoWhere to buy it: auto (let the site find it), own (the user's links), none.
is_matureYes18+ (adult content, firearms or firearm parts, graphic content). Always ask.
visibilityYesThe user's choice. Always ask.
descriptionYesWhat the part is, at least 80 characters, from what the user and the CAD say.
image_pathsYesAt least one picture of the part (JPEG, PNG, GIF or WebP).
image_captionsNoOne caption per image, or none.
datasheet_pathsNoPDF datasheets. Attach the part's datasheet when it has one.
readme_markdownYesMarkdown with the sections What it is, Dimensions, How to use and Materials (at least ~400 characters). Never invent dimensions.
datasheet_titlesNoOne title per datasheet, or none.

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 already declare a non-read-only, open-world, non-destructive, non-idempotent write. The description adds context annotations cannot carry: a documentation completeness gate that aborts the upload, moderation parity with the website, and the return value (page link). It doesn't quantify the moderation delay or say what happens to files on partial 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?

Front-loads the action and destination, then the gating conditions and return value; five sentences all carry information. The precondition sentence is dense and slightly tangled ('said yes and chose the visibility, the licence (for public) and whether it's 18+'), but nothing is padding.

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?

For a 13-parameter, 7-required mutation with no output schema, the definition covers preconditions, the abort condition, moderation and the returned link — enough to call it correctly. It is silent on size limits, upload duration, and failure/retry behaviour, which matter for a non-idempotent upload.

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 high (85%), so the schema already documents paths, visibility, licence, maturity and caption conventions. The description only echoes the ask-the-user rules for visibility, licence-for-public and 18+, which the schema states independently, adding little new parameter meaning.

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 ('Upload a new model to CommunityCAD'), names the source forms (file or folder), the payload (pictures, README, optional datasheets), and the visibility dimension. The word 'new' implicitly separates it from upload_version, so an agent can distinguish intent without opening either 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?

Gives a hard precondition — the user must have explicitly said yes and chosen visibility, licence (for public) and 18+ status — plus a when-not rule ('Nothing is uploaded when documentation is missing'). It does not name a sibling alternative for adding images/datasheets to an existing model, but the guidance for this tool's own use is clear.

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