Skip to main content
Glama

list_coupon_brands

Read-onlyIdempotent

Lists every store chain with a CouponJP tourist coupon, showing category, top discount, store count, and coupon page link for quick comparison.

Instructions

List every store chain with a CouponJP tourist coupon: category, top discount, number of stores and coupon page link.

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

Input Schema

NameRequiredDescriptionDefault
languageNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description usefully discloses the shape of the results but says nothing about result volume, ordering, caching, or that currency/discount values may be locale-dependent. Minor added 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?

A single tight sentence with the scope front-loaded and the payload fields listed after the colon. No redundant phrasing, though it reads as a comma list rather than a structured summary.

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?

For a simple read-only listing tool with no output schema, the description covers what the tool returns field-by-field, which is exactly the missing piece. The only real gap is the undocumented language parameter and absence of any routing hint to detail tools.

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?

One optional parameter (language) with 0% schema description coverage; the description never mentions it, so an agent would not learn from the text that results can be localized. The schema's default 'en' and the title 'Language' still make the parameter largely self-explanatory, keeping this at the minimum-viable level.

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 ('List every store chain with a CouponJP tourist coupon') and enumerates the returned fields (category, top discount, store count, coupon page link). This is clearly distinguishable from sibling tools like find_coupon_stores or brand_coupon, though it never names an alternative explicitly.

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 by 'List every store chain' – an agent can infer this is the browse/discovery entry point versus per-store lookups in siblings. However, there is no explicit when-to-use or when-not-to-use guidance, and no mention of what to call next for detail on a specific brand.

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