Skip to main content
Glama
Dicker Data MCP Server

Dicker Data MCP Server

by WYRE-AI

dickerdata_get_price

Look up Dicker Data price-list pricing and stock-on-hand for a single product code to check available price and inventory.

Instructions

Look up Dicker Data PricingRequest price-list (datafeed) pricing and stock-on-hand for a single product code. UnitPrice and SOH come from Dicker's PricingRequest feed and may lag your live account price and stock; dimensions may be null. No quantity-based pricing (PricingRequest has no quantity field). Currently uses the same PricingRequest feed as dickerdata_get_pricing, not Dicker's live GetPrice endpoint.

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": {
      "productCode": "<productCode>"
    },
    "name": "dickerdata_get_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
productCodeYesThe Dicker Data product/part number to price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.4
    • removedInput schema / properties / quantity
      Removed value: -{
      -  "description": "Quantity to price at. Defaults to 1 if omitted.",
      -  "type": "number"
      -}
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that prices and SOH come from a datafeed that may lag the live account, that dimensions may be null, and that this does not use Dicker's live GetPrice endpoint. It omits auth/permission needs and error behavior for an unknown product code, which keeps it below a 5.

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?

The description is front-loaded with what is returned before the caveats, and every sentence carries operational information. It is dense but not padded; the final sentence about the shared feed could be folded into the earlier caveat for tighter flow.

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 read lookup with no output schema and no annotations, the description covers the important unknowns: data staleness, nullable fields, and the missing quantity dimension. What is absent — behavior on an invalid product code and returned record shape — is modest relative to the tool's simplicity.

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 description coverage is 100% and the single productCode parameter is already documented in the schema. The description reinforces that it expects one product code, but adds no format, casing, or example syntax beyond what the schema supplies, 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 gives a specific verb and resource: look up PricingRequest price-list pricing and stock-on-hand for a single product code, naming the returned fields (UnitPrice, SOH). It even names the sibling dickerdata_get_pricing, but only to say they currently share a feed, which blurs rather than sharpens the distinction between the two tools.

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

Usage Guidelines3/5

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

It implies usage ('for a single product code') and rules out one case (no quantity-based pricing since PricingRequest has no quantity field). However, it never tells the agent when to prefer this over dickerdata_get_pricing, and admits they hit the same feed — an agent gets no decision rule between two near-identical siblings.

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