Skip to main content
Glama

Resolve a part number against a datasheet's own legend

datasheetvend_resolve_part_number
Read-onlyIdempotent

Resolve a full ordering code against a datasheet your account already extracted with the part_decoder module: the document's own part-number legend and ordering table, as that run read them. Returns the status verbatim, each parsed position with its meaning, page and snippet, any unexplained characters, the ordering-table match and the merged package and temperature facts. The meaning is the document's own legend: fully_decoded is NOT 'orderable' (every character is explained but the code is not in the ordering table), ambiguous lists every reading and picks none, and a family legend can define codes for sibling parts. State a code as the part's identity only when answer.may_assert_identity is true. A run with no part-number grammar is refused (NO_UNIVERSAL_BLOCK), never guessed. No new extraction. 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": {
      "job_id": "<job_id>",
      "part_number": "<part_number>"
    },
    "name": "datasheetvend_resolve_part_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesAn extraction job in your account that ran the part_decoder module.
part_numberYesThe full ordering code to resolve, as printed (for example 'STM32F103C8T6TR').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, closed-world, non-destructive) it discloses that the tool is deterministic, calls no model, extracts nothing new, costs no credits, requires an API key, and refuses outright with NO_UNIVERSAL_BLOCK when no part-number grammar exists rather than guessing. It also explains what the returned status values mean, which is exactly the behavioral context an agent needs before trusting a result.

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 purpose, then interpretation rules, then cost/determinism facts; nearly every sentence carries information. The opening sentence is long and multi-clausal, which slightly hurts scannability, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 takes on the burden of describing returns and does so concretely: verbatim status, parsed positions with meaning, page and snippet, unexplained characters, ordering-table match, and merged package/temperature facts. For a two-parameter, read-only, deterministic tool this is complete.

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, but the description adds meaning: the code must be the *full* ordering code as printed, and job_id must reference a job that specifically ran the part_decoder module. That constrains parameter selection beyond the schema's plain string descriptions.

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 states a specific verb and resource ('Resolve a full ordering code against a datasheet your account already extracted') and pins the scope to the document's own legend and ordering table as read by a prior part_decoder run. That distinguishes it in substance from a generic decoder, though it never names datasheetvend_decode_part_number, so the contrast is inferred rather than stated.

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?

It gives clear preconditions (the job must have run the part_decoder module) and explicit interpretation rules: fully_decoded is not 'orderable', ambiguous picks no reading, and identity may only be asserted when answer.may_assert_identity is true. What is missing is an explicit 'use X instead when...' routing statement to the sibling decoder tool.

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