PartsPlan

Check stock and prices

check_stock

Read-only

Checks current stock, prices, lead times and lifecycle labels from DigiKey, Mouser, element14 and TME for up to three exact manufacturer part numbers. Use when the user asks for a current stock or price check. Results stay separate by distributor, with retrieval times and official product links; values are as each distributor reports them (no currency conversion). Not for datasheet specifications, substitute validation, ordering, bulk collection or monitoring. Each part checked uses 5 allowance units.

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": {
      "parts": "<parts>"
    },
    "name": "check_stock"
  }
}

Input Schema

Name	Required	Description	Default
`parts`	Yes	1 to 3 parts.

Output Schema

Name	Required	Description	Default
`note`	Yes
`parts`	Yes
`usage`	Yes
`status`	Yes
`message`	No
`retryable`	No
`checked_at`	Yes
`doc_sha256`	No
`request_id`	Yes
`retry_after_ms`	Yes
`schema_version`	Yes
`withdrawn_note`	No
`withdrawn_documents_omitted`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly/openWorld/idempotent=false): it states results are kept separate per distributor, include retrieval times and official product links, are reported as-is with no currency conversion, and that each part consumes 5 allowance units. That is exactly the operational context an agent needs before spending a quota.

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?

Five tightly packed sentences, front-loaded with the capability, then usage, then exclusions, then cost. No filler or repetition; each sentence adds a distinct decision-relevant fact.

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?

Even though an output schema exists, the description sketches the result shape (per-distributor groups, retrieval times, product links) and the no-conversion caveat, plus the quota cost. Nothing needed 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.

Parameters4/5

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

Schema coverage is 100% and already documents mpn (exact, suffixes matter), brand, and the 1-3 item bound with nested descriptions. The description reinforces the 'exact' requirement and the three-part cap, which is useful emphasis but largely restates what the schema already says, so it sits just above the baseline.

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 ('Checks current stock, prices, lead times and lifecycle labels'), names the four distributors, and bounds the scope to 'up to three exact manufacturer part numbers'. This clearly separates it from siblings like search_parts (discovery) and find_datasheet (specs).

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?

'Use when the user asks for a current stock or price check' gives the trigger, and 'Not for datasheet specifications, substitute validation, ordering, bulk collection or monitoring' explicitly rules out the adjacent sibling use cases. The quota cost is also disclosed so the agent can judge when it is worth calling.

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

All PartsPlan tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.