Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Search a datasheet

search_datasheet
Read-only

Search a model's datasheets for pages mentioning a term such as mounting holes, returning snippets and links for follow-up reading.

Instructions

Find pages in a model's datasheets that mention something (e.g. 'mounting holes'). Returns pages with short snippets and links; follow up with read_datasheet.

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>",
      "query": "<query>"
    },
    "name": "search_datasheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
model_idYes

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 and openWorldHint, so safety is covered; the description adds the return shape ('pages with short snippets and links') and the intended follow-up call, which is real behavioral value given there is no output schema. It omits pagination/limit behavior and how snippets are truncated, keeping it below a 5.

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, zero filler, with the core action front-loaded and the follow-up instruction placed after the return description. Every clause carries information.

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?

Purpose, return shape, and workflow are covered adequately for a three-parameter read tool, and annotations handle the safety profile. However, with no output schema and 0% schema description coverage, the unexplained limit and model_id parameters leave the definition short of 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 description coverage is 0%, so the description carries the full burden, yet it only implicitly clarifies 'query' as a free-text mention search via the 'mounting holes' example. Neither model_id nor limit (default 10, max 20) is explained anywhere, leaving two of three parameters undocumented.

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 ('Find pages in a model's datasheets that mention something') with an inline example query, and explicitly positions itself as the precursor to read_datasheet. An agent can tell this apart from read_datasheet 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 clear usage context (locate pages by keyword) and an explicit next step ('follow up with read_datasheet'), which effectively routes the agent through a search-then-read workflow. It stops short of stating when not to use it or how it relates to list_datasheets, so it is clear context without full exclusions.

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