Skip to main content
Glama
Dicker Data MCP Server

Dicker Data MCP Server

by WYRE-AI

dickerdata_get_pricing

Retrieve price-list pricing and stock-on-hand for one or more Dicker Data product codes to check unit costs and availability.

Instructions

Look up Dicker Data PricingRequest price-list (datafeed) pricing and stock-on-hand for one or more product codes. UnitPrice and SOH come from Dicker's PricingRequest feed and may lag your live account price and stock; dimensions may be null.

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": {
      "productCodes": "<productCodes>"
    },
    "name": "dickerdata_get_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
productCodesYesOne or more Dicker Data product/part numbers to look up price-list pricing and stock for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.5
    • changedInput schema / properties / productCodes / description
      Previous value: -"One or more Dicker Data product/part numbers to price and check stock for."New value: +"One or more Dicker Data product/part numbers to look up price-list pricing and stock for."
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does add real behavioral context: results originate from an external datafeed, may be stale relative to the live account, and individual fields ('dimensions') may be null. It omits permission requirements, rate limits, and batch-size limits, but the freshness/nullability disclosures are the operationally important ones for a read lookup.

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 tight sentences with the core purpose front-loaded and the caveats second — no filler. Minor deduction for the phrase 'dimensions may be null', which is ambiguous about what 'dimensions' refers to (fields? attributes? SKU dimensions?), leaving a small ambiguity in an otherwise crisp statement.

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 lookup with no output schema, the description covers the essentials and additionally names the two key return fields (UnitPrice, SOH), which compensates for the absent output schema. It leaves the exact response shape (array? per-code mapping? partial failures?) unspecified, which is the main remaining gap.

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?

With 100% schema coverage and a single parameter, the schema already documents productCodes fully, including that it is an array of part numbers. The description only reiterates the batch nature ('one or more product codes') without adding format, normalization, or limit details, 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 description names a specific verb ('Look up') and a precise resource ('price-list (datafeed) pricing and stock-on-hand') plus the source system (Dicker's PricingRequest feed) and supports batch lookup. It implicitly distinguishes itself from the single-price sibling dickerdata_get_price via 'one or more product codes' and the datafeed framing, but never names or contrasts that sibling explicitly.

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 context for when this data is appropriate: price-list/feed pricing and SOH, with an explicit warning that these 'may lag your live account price and stock' — steering agents away from treating results as authoritative. It does not explicitly route the agent to an alternative tool (e.g. dickerdata_get_price for live account pricing), so no true exclusion guidance.

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