Skip to main content
Glama

brand_coupon

Read-onlyIdempotent

Retrieve coupon details for a Japanese retail brand, including purchase or product discounts, validity, tax refund fees, and the coupon page link.

Instructions

Coupon details for one chain (e.g. "Don Quijote", "Daimaru", "Kokumin"): discount by purchase amount or product type, validity, the store's tax refund fee and the coupon page link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "brand": "<brand>"
    },
    "name": "brand_coupon"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYes
languageNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the operation as read-only, non-destructive, idempotent, and open-world. The description adds useful behavioral context by listing the kinds of information returned: discounts by purchase amount or product type, validity, tax refund fee, and coupon page link.

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?

The description is a single front-loaded sentence with no filler. The parenthetical brand examples and colon-separated list of returned details are dense but useful.

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 simple read-only lookup with rich annotations, the description covers the core result contents and brand examples. However, it leaves the language parameter, brand matching expectations, and not-found behavior unaddressed, which are clear gaps even for a low-complexity tool.

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?

Schema coverage is 0%, so the description has to carry parameter meaning. It partially compensates by explaining that 'brand' is a chain name and giving examples like Don Quijote, Daimaru, and Kokumin, but it says nothing about the 'language' parameter beyond its schema name.

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 clearly identifies the resource and scope: coupon details for a single chain, with concrete examples of chains. It does not explicitly contrast itself with siblings such as list_coupon_brands or find_coupon_stores, but the 'one chain' scope gives an implicit distinction.

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: call this when you need coupon details for a specific brand. There is no explicit when-to-use versus alternatives, no exclusions, and no guidance on using list_coupon_brands or find_coupon_stores first.

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