Skip to main content
Glama

get_registry_part

Retrieve the full registry record for one part, including footprint, symbol and 3D model download URLs, datasheet link, dimension origin, and real-build reports.

Instructions

Give the full record of one part of the parts registry.

The record has the download URLs (footprint, symbol, 3D model), the link to the datasheet, the origin of the dimensions, and the reports of real builds.

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_id": "<part_id>"
    },
    "name": "get_registry_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
part_idYesThe ID of the part (search_parts_registry gives it).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully enumerates what the record contains (download URLs for footprint, symbol, 3D model; datasheet link; dimension provenance; real build reports), which tells the agent what to expect from the result, but it says nothing about whether the call is read-only, what happens on an unknown part_id, or error behavior.

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 that are front-loaded with the core action and then enumerate the payload contents. There is no filler or redundant restatement of the tool name.

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 tool with an output schema, an explicit annotation set absent, the definition covers purpose and payload shape adequately. The remaining gap is only the lack of explicit guidance on what a missing or invalid part_id does, which is minor given its simplicity.

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?

There is a single required parameter with 100% schema description coverage, and the schema already states it is 'the ID of the part' and points to search_parts_registry. The description repeats that the record is for 'one part' but adds no format or sourcing detail beyond the schema, so baseline 3 applies.

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 first sentence names a specific verb and resource ('Give the full record of one part of the parts registry') and scopes it to a single part, which distinguishes it from a list/search tool. It does not name a sibling explicitly in the main body, but 'full record of one part' contrasts clearly enough with search_parts_registry, which is referenced in the parameter description.

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: the part_id description parenthetically notes that 'search_parts_registry gives it', which hints at a search-then-fetch workflow. There is no explicit statement of when to use this instead of search_parts_registry or download_registry_part, and no exclusions or prerequisites.

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