Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Add datasheets

add_datasheets

Attach PDF datasheets to your own model after explicit confirmation; their text becomes searchable within minutes.

Instructions

Attach PDF datasheets to the user's own model (their text becomes searchable after a few minutes). Only after the user's explicit yes.

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>",
      "paths": "<paths>"
    },
    "name": "add_datasheets"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYesPDF datasheets.
titlesNoOne title per datasheet, or none.
model_idYesThe user's own model (id or page URL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts: text becomes searchable only after a few minutes (asynchronous indexing, so immediate reads via search_datasheet may miss it), the operation is scoped to the user's own model, and human consent is mandatory.

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

Conciseness5/5

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

Two sentences, zero filler, with the core action front-loaded and the two constraints (indexing delay, consent) trailing as parenthetical caveats. Every clause carries information an agent needs.

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 3-parameter write tool with full annotation coverage and no output schema, the description covers the essential unknowns: consent gate, ownership restriction, and indexing latency. It omits edge behavior such as partial-failure handling when attaching multiple PDFs or file-size/type rejection, which keeps it just short of 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?

Schema coverage is 100% — paths, titles (one per datasheet or none), and model_id (id or page URL) are all documented in-schema, including the max of 5 files. The description adds no further parameter-level detail such as what happens when titles length mismatches paths, so the baseline 3 applies.

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 pairs a specific verb ("attach") with a specific resource ("PDF datasheets") and a bound target ("the user's own model"), which is far more informative than the title alone. It does not name or contrast with a sibling such as add_images or list_datasheets, so an agent must infer the boundary from the file type.

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?

"Only after the user's explicit yes" gives a concrete precondition for invocation, and "the user's own model" excludes attaching to other people's models. What's missing is routing guidance against alternatives (e.g. when to use add_images or upload_version instead), so it stops short of a full when/when-not statement.

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