Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Read a datasheet

read_datasheet
Read-only

Extracts OCR text from datasheet pages with page markers so you can cite sources, check part specifications, and include the datasheet and model URLs used.

Instructions

OCR text of a datasheet's pages, with page markers so you can cite the page. Always give the user the datasheet_url and model_url you used.

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>",
      "datasheet_id": "<datasheet_id>"
    },
    "name": "read_datasheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_idYes
last_pageNoDefaults to first_page + 4. At most 20 pages per call.
first_pageNo
datasheet_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3/5.0
Behavior3/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 usefully adds that the return is OCR text with page markers suitable for citation, which annotations do not convey. It says nothing about pagination limits (only the schema's last_page field mentions the 20-page cap) or what happens when the requested range exceeds the document.

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, front-loaded with what the tool returns and followed by a single operational rule; nothing is padded. The second sentence's reference to "datasheet_url and model_url" is slightly opaque since those names do not match any parameter, which costs a point.

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?

With no output schema, the description rightly explains the return value (OCR text plus page markers) and thus carries that burden well. However, for a four-parameter tool with 25% schema coverage, it leaves the two required identifier parameters unexplained and gives no hint about range/pagination behavior beyond the schema, so it is only partially complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 25%: only last_page is described in the schema, while model_id, datasheet_id, and first_page are bare titles. The description does not compensate — it never explains what model_id or datasheet_id identify, nor how first_page interacts with the defaulted last_page range, despite referencing model_url and datasheet_url in passing.

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?

"OCR text of a datasheet's pages, with page markers" states a specific verb-equivalent (extract OCR text) and resource (datasheet pages), and it clarifies the output shape. It stops short of explicitly distinguishing itself from the sibling search_datasheet, so an agent must infer that this retrieves page content for a known datasheet rather than searching.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative is named even though search_datasheet exists as an obvious sibling. The second sentence ("Always give the user the datasheet_url and model_url you used") is a citation obligation on the response, not invocation guidance.

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