Skip to main content
Glama

AgentShopping

search_offers

Search AgentShopping offers. If sample_data is true, prices are fictional and must not be quoted as live offers. Ranking never uses commission. Each offer includes tracked_url (/go/), currency, country, and coupons with validity and price_after when unambiguous. Shop links are affiliate ads.

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

Input Schema

NameRequiredDescriptionDefault
qNo
langNo
limitNo
countryNoISO 3166-1 alpha-2, or ALL
categoryNo
currencyNoISO 4217

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the sample-data caveat, the commission-neutral ranking rule, the affiliate nature of shop links, and the response field set. It leaves out pagination behavior for limit, auth requirements, and rate limits, which are the remaining gaps for a mutation-free search tool.

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?

Five compact sentences, front-loaded with the core action, with no filler. The return-shape sentence is dense but justified given there is no output schema; the only cost is that output detail crowds out any input parameter explanation.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter tool with no annotations and no output schema, the definition covers output shape and key caveats adequately, but omits all input parameter semantics and never reconciles the referenced sample_data flag with the schema. An agent can call it and interpret results, but cannot confidently set q, limit, lang or category.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, so the description should compensate for q, lang, limit and category, but it says nothing about any of them. Instead it explains return fields (tracked_url, currency, country, coupons), and it references a "sample_data" flag that does not appear in the input schema at all, which muddies rather than clarifies parameter meaning.

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 AgentShopping offers") and implies the result unit is an offer, which distinguishes it from siblings dealing in products, stores, merchants or coupons. It stops short of naming an alternative or stating the scope boundary explicitly, so differentiation is inferred rather than declared.

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?

Provides real usage constraints — do not quote sample_data prices as live, ranking is not commission-influenced, links are affiliate ads — which shape how results may be presented. However it never says when to choose this tool over find_stores_for, get_product, list_coupons or list_merchants, so selection guidance is only implied.

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