Well Told

Search Well Told corporate catalog

search_catalog

Read-onlyIdempotent

Searches Well Told's catalog of custom gifts for clients, employees, teams and events: glassware, tumblers and bottles personalized with a map of a meaningful place, a logo or text. Use it when someone is looking for custom, branded or personalized gifts in quantity. Filters by budget per unit, quantity (minimum order and volume pricing), category, and in-hand date (lead time). Returns each product's id, live price, minimum, estimated delivery date, the design types it offers (map_logo, logo_only) and its Logo Only areas.

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_catalog"
  }
}

Input Schema

Name	Required	Description
`category`	No	Product type or family, e.g. 'glassware', 'tumbler', 'bottle', 'rocks'
`occasion`	No	Occasion or recipients, e.g. 'client thank-you', 'new hires'
`quantity`	No	Number of gifts
`in_hand_date`	No	Date the gifts must arrive, YYYY-MM-DD
`budget_per_unit`	No	Budget per gift in US dollars

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and idempotency need no restating. The description adds genuinely new behavioral detail: the filters are soft (all optional) and the response includes live price, minimum, estimated delivery and supported design types. It still says nothing about result limits, pagination, or what an empty result means, which matters for a search tool with no output schema.

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?

Three sentences, front-loaded with the what and the when, then the filter list, then the return shape — a sensible order. The middle sentence is dense with stacked parentheticals ('quantity (minimum order and volume pricing)') but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 return contract itself and does so: product id, live price, minimum, estimated delivery date, supported design types and Logo Only areas. Combined with a fully documented five-parameter schema and safety annotations, an agent has everything needed to call this correctly.

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 baseline is 3, but the description earns a bump by explaining what two parameters actually drive: quantity implies 'minimum order and volume pricing', and in-hand date maps to 'lead time' rather than a ship date. It also frames budget as 'per unit', clarifying the pricing basis. The 'occasion' parameter is not mentioned at all in the description.

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 opens with a specific verb and resource ('Searches Well Told's catalog of custom gifts') and enumerates the product families covered (glassware, tumblers, bottles) plus the personalization types. It does not name a sibling such as show_products or get_quote, so an agent must infer the boundary between browsing versus searching, which keeps this just below a 5.

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?

'Use it when someone is looking for custom, branded or personalized gifts in quantity' gives a clear triggering condition, including the quantity qualifier that rules out single-item or personal use. No explicit exclusions or alternative tools are named, so there is no routing guidance for cases like getting a price quote or a proof.

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

All Well Told tools Inspect

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

Need Help?