Skip to main content
Glama

Buy a part pack

datasheetvend_get_part_pack

Buy one part pack: a component's frozen module outputs (pinout, footprint, limits, timing and the others the manifest lists) as one JSON envelope. Price: 3 module credits with a DatasheetVend API key, charged once per account (the same pack again is free), or $2.00 per call with a Stripe machine payment (no account, so each call pays). The pack is found before anything is charged: a missing pack, an unnamed package when several are shelved, or a pack too large for one answer costs nothing. Read the free manifest first: a pack may cover only some modules. The manufacturer's PDF is linked, never included. This is not the $19 Verified Pack sold on the website.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageNoPackage slug from the manifest (e.g. 'tqfp-32'). Required when more than one package is shelved; null or empty means not given.
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.7/5.0
Behavior5/5

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

Goes well past the annotations by disclosing pricing models (3 credits with an API key, charged once per account; $2.00 per call via Stripe with no account), the charge-ordering guarantee ("The pack is found before anything is charged"), and three failure modes that are free. It also states a content boundary ("The manufacturer's PDF is linked, never included") that the annotations say nothing about. The idempotentHint=false annotation is compatible: repeat calls still execute, they are merely not re-charged.

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 purpose, then pricing, then caveats, with no filler sentences. The pricing sentence is long and packs three conditions into one line, which costs a little readability, but every sentence carries distinct information.

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 paid, mutating, three-param tool with no output schema, it covers cost, charge timing, prerequisites, failure behavior, and content scope. The only soft gap is that the shape of the returned envelope beyond the field list is left vague, though the manifest is named as the authority for which modules appear.

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 schema already documents all three parameters and the baseline is 3. The description adds real meaning on top: it explains that an unnamed package when several are shelved results in a free miss, clarifying the runtime consequence of leaving the package param null, which the schema does not state.

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?

Specific verb and resource: "Buy one part pack: a component's frozen module outputs ... as one JSON envelope," and it enumerates what the envelope contains (pinout, footprint, limits, timing). It also explicitly separates itself from the sibling manifest tool and from the unrelated $19 Verified Pack, so an agent can pick it out without opening a schema.

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?

Gives an explicit prerequisite/ordering rule ("Read the free manifest first: a pack may cover only some modules") naming the sibling to call beforehand, and names a specific tool it is not (the $19 Verified Pack). It also tells the caller the failure conditions under which no charge occurs, which is when-not-to-worry guidance an agent can act on.

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