Skip to main content
Glama

Match chips to official KiCad footprints

datasheetvend_match_kicad_footprint
Read-onlyIdempotent

Find the official KiCad library footprint for chips from their package numbers. An id comes back only when pin count, pitch and body size agree on source evidence and exactly one official footprint fits; otherwise the status is 'ambiguous' (with the candidates and what separates them) or 'unresolved' (with the reason), and footprint_id is null, because a wrong footprint on a board is worse than none. choices records an engineer's pick among the candidates of an ambiguous chip; a pick that is not a candidate is ignored and listed with its reason. Numbers in, library ids out: no job data is read. Deterministic: runs DatasheetVend's checks in code, calls no model and extracts nothing. Costs no credits. Needs a DatasheetVend API key.

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": {
      "chips": "<chips>"
    },
    "name": "datasheetvend_match_kicad_footprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
chipsYes1-40 chips
choicesNoAn engineer's pick for ambiguous chips: chip id to footprint id, honoured only when it is a candidate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds material context beyond them: deterministic code-only checks with no model call, zero credit cost, a required DatasheetVend API key, and the safety rule that a null footprint_id is preferred over a wrong match. It also discloses that a non-candidate pick in `choices` is ignored and reported with its reason.

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?

Front-loaded with the verb and the resolution rule, then behavior and cost. A few phrases overlap ('no job data is read', 'extracts nothing', 'calls no model'), but each reinforces a distinct guarantee, so almost nothing is wasted.

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?

With no output schema, the description must carry the return contract, and it names the key outcomes (footprint_id, ambiguous with candidates and their differences, unresolved with a reason, ignored choices). It does not enumerate the full success payload, but the decision-relevant shape is covered for a 2-parameter nested-input tool.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description goes further by explaining that matching requires pin count, pitch and body size to agree on source evidence, which gives meaning to the source/inferred `basis` markers in the schema. It also clarifies the ignore-and-report semantics of `choices` entries that are not candidates.

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 the official KiCad library footprint for chips from their package numbers') and scopes it precisely with 'Numbers in, library ids out: no job data is read', which separates it from the extract_* siblings that read job data. An agent can tell what this returns and what it does not.

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?

Makes clear the input precondition (package numbers must already exist, no job data is read) and explains the ambiguous/unresolved outcome paths plus how `choices` is used. It stops short of naming the alternative tool to call when package numbers have not been extracted yet, so the routing guidance is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources