Skip to main content
Glama

List Dealer Offers

list_dealer_offers
Read-only

List a dealer's current public offers, stalest first by default, with prices, stock and verification status, observation timestamps, and computed age. Use this as a self-service stale-offer audit.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of offers to return (default 50, hard cap 100).
offsetNoNumber of stalest-first offers to skip (default 0).
dealerIdYesDealer ID or slug (e.g., 'jm-bullion', 'JM Bullion', or 'jmbullion.com').
inStockOnlyNoIf true, return only offers whose stock status is in_stock.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, and the description adds genuinely new behavior: default ordering is stalest-first, results are paginated in that order, and the payload includes observation timestamps and computed age. It doesn't state auth requirements, rate limits, or behavior for an unknown dealer slug, which keeps it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the resource and ordering rule before the intended use. No redundant restatement of the name or schema.

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 no output schema, the description usefully enumerates the returned fields and the default sort, which is what an agent needs to decide whether to call it. Missing only secondary details such as total-count/pagination signaling and error behavior for an invalid dealer ID.

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 a 3 is the baseline, but the description adds ordering semantics that the schema doesn't state — "stalest first by default" — which changes how the agent should interpret limit and offset. That is real meaning beyond the parameter descriptions.

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 ("List a dealer's current public offers") and enumerates the fields returned (prices, stock, verification status, timestamps, computed age), so the agent knows exactly what it gets. It does not explicitly distinguish itself from siblings like list_verified_dealers, leaving that differentiation to inference from the verb/resource pairing.

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 offers one concrete use case ("a self-service stale-offer audit"), which implies when to reach for it, but gives no when-not guidance and names no alternative for the adjacent needs its siblings cover (e.g., dealer verification, price positioning).

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