SAGE Infinite Search

search

Read-only

Search SAGE-connected stores and SAGE's verified public independent-retailer inventory network for a specific rare, vintage, discontinued, one-of-one, local, secondhand, or hard-to-find general-audience physical product. Results require fresh positive source evidence, a crawlable SAGE item page, and the underlying exact retailer source when fetched. When results is empty, show recovery.markdownLink to the shopper. Read-only: this tool cannot reserve, purchase, contact a retailer, or change inventory.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	The shopper's product request, including useful traits and location words they supplied.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes
`recovery`	No

TDQS

A4.1/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. The description reinforces the read-only nature and adds context about result requirements and empty result behavior. No contradictions. It adds value beyond annotations.

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?

The description is moderately concise but front-loaded with the most important information. Each sentence serves a purpose: what it searches, requirements, error handling, and limitations. Could be slightly trimmed but remains efficient.

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?

Given the tool's simplicity (1 parameter, output schema exists, annotations present), the description covers the essential aspects: purpose, constraints, and behavior. It is sufficiently complete for an AI agent to use correctly.

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?

The schema description for the single 'query' parameter is clear (100% coverage). The tool description does not add significant additional meaning for the parameter; it repeats the types of products. Baseline 3 is appropriate.

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?

The description clearly states the tool searches SAGE's store and inventory network for specific hard-to-find products. It uses a specific verb ('Search') and resource ('stores and inventory network'), and the scope is well-defined (rare, vintage, discontinued, etc.). This distinguishes it from the sibling 'fetch' tool.

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

Usage Guidelines4/5

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

The description outlines conditions for use: results require fresh evidence, a crawlable page, and retailer source. It also specifies what the tool cannot do (reserve, purchase, etc.) and provides guidance for empty results. However, it does not explicitly compare with sibling tools like 'fetch'.

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

All SAGE Infinite Search tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

The two tools, 'search' and 'fetch', have clearly distinct purposes: one retrieves a list of results based on a query, the other gets details for a specific result ID. No overlap or ambiguity.

Naming Consistency4/5

Both tool names are single imperative verbs ('search', 'fetch'), which is consistent in style. While not following a standard verb_noun pattern, they are uniform and clear.

Tool Count4/5

With only two tools, the server is very focused. This is appropriate for a specialized search service, though a few more tools (e.g., for filtering or pagination) might improve utility.

Completeness3/5

Essential operations are covered: querying and fetching details. However, missing features like filtering, sorting, or pagination could limit the agent's ability to handle non-trivial searches effectively.

Resources

Need Help?