Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

List datasheets

list_datasheets
Read-only

Retrieve metadata and links for a model's datasheets, including file names, page counts, sizes, and OCR availability, without downloading files.

Instructions

A model's datasheets: file name, pages, size, whether OCR text is available, and links. Reading datasheets never uses a download.

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

Input Schema

NameRequiredDescriptionDefault
model_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's real contribution is the statement that reading datasheets never consumes a download — a genuine cost/side-effect disclosure not captured by the annotations. It also discloses the returned field set in the absence of an output schema, though it says nothing about result size, pagination, or what an empty result means.

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 short sentences with zero filler: the resource and return fields come first, followed by the one behavioral caveat. Every clause earns its place.

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 one-parameter read-only lister with no output schema, the description covers what is returned and the no-download behavior, which is most of what an agent needs. Remaining gaps are the boundary against read_datasheet/search_datasheet and any pagination or result-count behavior.

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 0%, so the schema documents nothing about model_id, and the description must compensate. The phrase 'A model's datasheets' does establish that the single parameter is a model identifier, which is the key semantic need here, but no format, source, or validity guidance is given.

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 names the resource (a model's datasheets) and enumerates the returned fields — file name, pages, size, OCR availability, links — so the agent knows exactly what comes back. The verb is implicit rather than stated (the title supplies 'List'), and it never names read_datasheet or search_datasheet as the contrasting siblings.

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?

The clause 'Reading datasheets never uses a download' implies a when-to-use rule (prefer this over download_file/check_download when you only need metadata or OCR status). However, it gives no explicit guidance on when to choose this versus read_datasheet or search_datasheet, so the agent must infer the boundary.

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