Skip to main content
Glama

See a part's shelved packs

datasheetvend_get_part_pack_manifest
Read-onlyIdempotent

See what DatasheetVend has shelved for a part BEFORE buying: each package variant's part pack, with the modules it holds and the ones it does not (module_count_available of module_count_total), its warnings, the source jobs and the manufacturer datasheet link. A missing part answers 'no shelved pack'. Free, no API key, no model call. Buy a pack with datasheetvend_get_part_pack.

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": {
      "vendor_slug": "<vendor_slug>",
      "part_number": "<part_number>"
    },
    "name": "datasheetvend_get_part_pack_manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
part_numberYesPart number, e.g. 'ATmega328P'.
vendor_slugYesVendor slug as in the component library, e.g. 'microchip'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With readOnly/idempotent/non-destructive annotations already establishing the safety profile, the description adds real value: it is free, requires no API key and no model call, and it specifies that an unknown part returns a 'no shelved pack' answer rather than an error. It stops short of stating response shape beyond the field inventory, keeping it at a strong 4.

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?

Two sentences, front-loaded with the pre-purchase purpose and the buy alternative. Dense but every clause contributes content; the parenthetical '(module_count_available of module_count_total)' is admittedly technical shorthand but earns its place by defining completeness.

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?

No output schema exists, yet the description enumerates what comes back (packs per package variant, covered vs missing modules, warnings, source jobs, datasheet link) plus the empty-result case. Nothing an agent needs in order to call this correctly is missing.

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 100% and both parameters are documented with examples, so the schema carries parameter meaning. The description references 'a part' and package variants but adds no format, normalization, or alternate-key hints beyond the schema; baseline 3 applies.

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 ('See what DatasheetVend has shelved for a part') and enumerates the returned contents: package variants, module coverage counts, warnings, source jobs, and datasheet link. It is clearly distinguishable from the sibling that purchases the pack.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames timing ('BEFORE buying') and names the alternative action with its tool ('Buy a pack with datasheetvend_get_part_pack'), so the agent knows which path to take. It also tells the agent what a missing part looks like, closing the main decision gap.

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