Skip to main content
Glama

AgentShopping

list_coupons

List coupons with valid_from and valid_until. Expired codes are omitted unless include_expired is true. Sample codes are labelled.

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": "list_coupons"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
countryNo
merchantNo
include_expiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the key default: expired codes are omitted unless include_expired is true, plus that sample codes are labelled in the output. It says nothing about pagination, result limits, or whether the merchant/country/lang filters are exact-match or partial, which leaves meaningful behavioral gaps for a four-parameter list 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?

Three short sentences, front-loaded with purpose and then the most decision-relevant behavior (the expired-code default). No filler, though the final sentence about sample codes is terse enough to be ambiguous.

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 read-only list tool with no output schema, the description adequately covers the return semantics (validity dates, sample labelling) but is incomplete on the three undocumented filter parameters, which are the main thing an agent must reason about when selecting arguments.

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 description coverage is 0%, so the description must explain all four parameters. It only clarifies include_expired; lang, country, and merchant are never mentioned, leaving the agent to guess whether they filter results, narrow scope, or affect localization of the returned 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?

The description opens with a specific verb and resource, 'List coupons', and adds that results carry valid_from and valid_until. That is concrete enough that an agent knows exactly what comes back, though it never distinguishes this from the other list/search siblings.

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 rather than stated: an agent can infer it should set include_expired when it wants historical codes, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for offer or merchant lookups.

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