Skip to main content
Glama

Get Dealer Price Position

get_dealer_price_position
Read-only

For one product, compare a dealer's delivered price with every other dealer's delivered price, return its rank and gap to the lowest offer, and compare its premium over spot with the field median.

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": {
      "slugOrId": "<slugOrId>",
      "dealerId": "<dealerId>"
    },
    "name": "get_dealer_price_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
dealerIdYesDealer ID or slug (e.g., 'jm-bullion', 'JM Bullion', or 'jmbullion.com').
slugOrIdYesProduct slug or canonical product ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description does add real behavioral value by naming the computed outputs (rank, gap to lowest, premium vs. median), which matters because there is no output schema. It stops short of disclosing edge-case behavior, such as what happens if the dealer does not carry the product, or whether 'delivered price' includes shipping/tax.

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?

A single sentence that front-loads the scope ('For one product') and then enumerates exactly what is returned. Every clause carries information; no filler, no restatement of the name.

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?

With two required, fully documented parameters and no output schema, the description does the necessary work of explaining what the response contains. What is missing is narrow but relevant: error/empty behavior when the dealer has no offer for the product, and the composition of 'delivered price'. For a read-only lookup of this complexity, it is otherwise complete.

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 dealerId field already documents the slug/name/domain forms, so the schema does the heavy lifting. The description contributes only the singular framing ('for one product', 'a dealer's'), reinforcing that both identifiers point at a single entity rather than a set. That is a small addition over an already-complete schema.

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: compare one dealer's delivered price against all other dealers for one product, and report rank, gap to lowest, and premium over spot versus the field median. That is far more precise than the title. It does not, however, distinguish itself from the sibling 'compare_product_dealers', which an agent could plausibly reach for the same task.

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?

The use case is implied clearly enough — you call this when you want a single dealer's competitive position on a product — but there is no explicit when-to-use statement, no exclusions, and no pointer to alternatives such as compare_product_dealers or get_premium_index. Usage has to be inferred from the computation described.

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