Skip to main content
Glama

attach_datasheet

Record which datasheet a part's pins came from by saving its link, title, and pin-table pages to part.yaml and verification.md; the link is not fetched.

Instructions

Record the datasheet a part's pins came from (link, title, pages) in part.yaml and verification.md. The link is not fetched.

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": {
      "part": "<part>",
      "url": "<url>"
    },
    "name": "attach_datasheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttp(s) link
partYesLibrary part id
pagesNoPin table pages, e.g. "3-4"
titleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full load, and it does disclose two non-obvious facts: it writes into part.yaml and verification.md, and it does not fetch the link. It still omits whether an existing datasheet entry is overwritten or appended, what happens on invalid URLs, and whether the files must exist beforehand.

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 write targets front-loaded and the important no-fetch caveat placed immediately after. Nothing could be removed without losing meaning.

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?

For a mutation tool with no annotations and no output schema, the description covers what is written and where, plus the no-fetch behavior. It still leaves gaps on repeat-invocation semantics and failure modes, which matter for a tool that edits project files.

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 75%, so the baseline is 3, and the description adds only modest value: it clarifies that 'link' means the url is stored rather than resolved, and that title/pages are part of the provenance record. The generic 'part' id and the format of 'title' remain unelaborated beyond the schema.

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 a specific verb ('Record') and resource ('the datasheet a part's pins came from') and states the concrete write targets, part.yaml and verification.md. An agent knows exactly what the tool accomplishes; only an explicit contrast with a sibling would push it higher.

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?

Usage is only implied: it is used to capture datasheet provenance for a part's pins, and the parenthetical hints at the fields to supply. There is no statement of when to call it versus other options, no prerequisite (e.g. that the part must already exist), and no exclusions.

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