Skip to main content
Glama

find_coupon_stores

Read-onlyIdempotent

Locate stores in Japan near a specified place where a free CouponJP tourist coupon is accepted, with optional brand filtering and distance-sorted results.

Instructions

Find stores in Japan near a place where a free CouponJP tourist coupon works.

place: a shopping area (e.g. "Namba", "Shinjuku", "Ginza", "Shinsaibashi"), a city ("Osaka") or a train station name,
in English, Japanese, Chinese or Korean. Or give latitude and longitude instead.
brand: optional chain name to filter (e.g. "Don Quijote", "Sugi Pharmacy", "Bic Camera").
language: answer language code (en, zh-CN, zh-TW, ja, ko, th, vi, id, ms, fil, hi, fr, de, es, it, pt, ru).
one_per_chain_first: list the nearest store of each chain first (default), then the rest; false = strict distance order.
Returns each store's brand, discount, address, straight-line distance, coupon page link and Google Maps 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": "find_coupon_stores"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNo
limitNo
placeNo
languageNoen
latitudeNo
longitudeNo
radius_kmNo
one_per_chain_firstNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real behavioral value on top: the geographic restriction to Japan, the default ordering behavior (nearest store per chain first, then the rest), and the exact fields returned. It does not address no-results behavior or place-name matching fuzziness, which keeps it below a 5.

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 purpose sentence is front-loaded, then a labeled parameter block, then a one-line return inventory. Nothing is redundant, and the parenthetical examples and language code list carry information rather than filler. The inline coordinate alternative reads naturally within the place note.

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 an 8-parameter, read-only lookup with no output schema, the description covers purpose, input forms, ordering semantics, and returned fields, which is close to sufficient to call it correctly. The omission of radius_km and limit leaves the agent guessing about search breadth and result count, which is a real but narrow gap.

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?

With 0% schema description coverage the description must carry the parameters, and it largely does: 'place' gets accepted input kinds and multilingual examples, 'brand' gets chain examples, 'language' gets the full code enum, and 'one_per_chain_first' is defined along with its false case. Two meaningful parameters, radius_km and limit, are never explained, so it is not complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with explicit scope: 'Find stores in Japan near a place where a free CouponJP tourist coupon works.' This is clearly distinguishable from list_coupon_brands (enumerating brands) and brand_coupon (coupons for a brand) without needing to open either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The context for use is unambiguous: locate coupon-accepting stores near a shopping area, city, or station, or via coordinates. It gives concrete worked examples ('Namba', 'Osaka', 'Don Quijote') that show expected inputs. It does not name sibling tools or state when-not to use this one, so it stops short of a 5.

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