list_calibersEnumerate every canonical caliber IronScout recognizes, each flagged with whether a current market snapshot exists and its sample count. Calibers without a snapshot are still listed (with hasSnapshot: false).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint. Description adds that calibers without snapshots are still listed with hasSnapshot: false, providing useful behavioral detail.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, front-loaded with purpose, no extraneous words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple parameterless list tool, description covers the key output fields and behavior. Lacks detail on ordering or pagination, but annotations provide additional context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 0 parameters, so baseline is 4. Description adds no param info, but none is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool enumerates all canonical calibers with snapshot existence and sample count. It distinguishes from siblings like get_market_snapshot and list_retailers.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. Does not mention exclusions or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action: market statistics, product lookup, caliber directory, retailer directory, and offer search. There is no meaningful overlap between get_product and search_offers because one is a direct single-item fetch and the other is a multi-result search.
All tools follow a consistent verb_noun pattern: get_ for single-item fetches, list_ for enumerations, and search_ for queries. The naming is uniform and predictable.
Five tools is well-scoped for a read-only market data service. Each tool covers a necessary capability without redundancy or bloat.
The tool set provides full coverage for its descriptive market-intelligence purpose: listing reference data (calibers, retailers), searching/fetching products and offers, and retrieving aggregate price statistics. No obvious CRUD or operational gaps exist because the service is explicitly read-only.