Skip to main content
Glama

agtmart sandbox store and agent survey

Search the sandbox catalog

search_products
Read-only

Search the agtmart sandbox catalog (20 fictional everyday products). Returns ids, prices in USD, stock, shipping_cost and estimated_total (price + shipping + estimated tax for one unit; e.g. coffee $9.99 -> est. total $15.80). Shipping is $4.99, free at $35+.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoKeywords, e.g. 'usb-c cable'
categoryNo
in_stockNo
max_priceNoMax item price in USD (before shipping and tax)
max_totalNoMax estimated delivered total in USD for one unit: price + shipping + estimated tax

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so the description's added value is the shipping rule ($4.99, free at $35+) and the estimated_total formula with a worked coffee example. That is genuine behavioral context an agent could not get from the annotations, though timing/pagination behavior and the default for limit remain unstated.

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?

Three front-loaded sentences: what it searches, what comes back, how totals are computed. The worked price example earns its place by making the tax/shipping arithmetic unambiguous.

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 six optional parameters and no output schema, the description does the heavy lifting by enumerating return fields and total composition. Remaining gaps — the default/meaning of limit, sort order, and empty-result behavior — are minor for a read-only catalog search.

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 50% (limit and in_stock are undocumented in both places), but the description compensates by explaining what estimated_total contains and pairing it with the shipping threshold, which makes the max_price vs max_total distinction concrete. That is meaning beyond the schema's terse parameter text.

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 and resource ('Search the agtmart sandbox catalog') plus the catalog's scope (20 fictional everyday products) and the fields returned. It does not explicitly contrast with the singular 'get_product' sibling, so an agent must infer that distinction from the names alone.

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?

Usage is implied — filtering a small catalog by keyword, category, price, and stock — but there is no explicit when-to-use statement, no exclusion, and no mention of the get_product alternative for known-item lookup.

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