Skip to main content
Glama

Search Bullion Catalog

search_bullion_catalog
Read-only

Search and filter OunceScout's canonical gold, silver, platinum, and palladium bullion catalog (coins, bars, rounds) with lowest verified dealer prices and multi-dealer offer counts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_bullion_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of products to return (1 to 25, default 10).
metalNoOptional metal filter.
searchNoOptional search keyword (e.g., 'American Eagle', 'Maple Leaf', '10 oz silver bar', 'Krugerrand').
matchedOnlyNoIf true, return only products with multiple compared dealers.
productTypeNoOptional product format filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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. The description adds that results carry lowest verified dealer prices and multi-dealer offer counts, which tells the agent what the payload contains. It says nothing about pagination, sorting, or what an empty result means, so the addition is useful but modest.

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?

A single front-loaded sentence that identifies the resource before the enrichment detail, with no filler. It is dense but every clause contributes scope information; only the trailing pricing clause could be trimmed.

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 carries the burden of describing returns and does so at a high level (prices and offer counts). For a five-parameter, all-optional read-only search tool this is nearly sufficient, though result ordering and pagination behavior remain unstated.

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%, with all five optional parameters individually documented including ranges, enums, and keyword examples, so the baseline of 3 applies. The description adds only indirect meaning, hinting that 'multi-dealer offer counts' relates to the matchedOnly flag, but it does not explain filtering interaction or default behavior beyond the 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?

States a specific verb (search and filter) and a specific resource (OunceScout's canonical bullion catalog), plus the scope of metals (gold, silver, platinum, palladium) and product formats (coins, bars, rounds). It also names the data enrichment (lowest verified dealer prices, multi-dealer offer counts), which separates it from a plain dealer-listing tool. It stops short of naming which sibling handles per-product dealer comparison.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. An agent must infer from the phrase 'search and filter catalog' that this is the browse/discovery entry point versus compare_product_dealers or list_dealer_offers, which is left entirely to inference.

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