Skip to main content
Glama
Sign In

OunceScout

by io.github.donofdebt
OverviewDiscussionsAdmin

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the default sort is stalest-first and the response carries computed age and observation timestamps, which tells the agent how results are ordered before it ever paginates.

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 sentences with zero filler. The resource, scope and ordering come first, followed by the intended use case, so the agent gets the essentials immediately.

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 four parameters, no output schema, and no nested objects, the definition covers what an agent needs: it enumerates the returned fields in lieu of an output schema and states the default ordering. The only shortfall is the absence of any note on pagination behavior or what an empty result means.

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%, so all four parameters are already documented, making 3 the baseline. The description reinforces the stalest-first ordering that governs what 'offset' skips and adds the 'current public' scope, but it contributes no new syntax or format detail beyond the schema.

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 ('List a dealer's current public offers') and goes further to name the ordering (stalest first by default) and the payload contents (prices, stock, verification status, timestamps, computed age). This is clearly distinguishable from siblings like compare_product_dealers or get_dealer_price_position, which do not enumerate offers.

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 closing sentence 'Use this as a self-service stale-offer audit' gives one implied scenario, which is better than nothing. However, it offers no when-not guidance and never names an alternative sibling for related tasks such as comparing offers or checking a dealer's price position.

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

All OunceScout toolsInspect
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.

Resources