Skip to main content
Glama

compare_shopping_cost

Read-onlyIdempotent

Compare what the same pre-tax yen purchase costs at drugstores, department stores, and duty-free shops after CouponJP coupons and tax-refund fees to find the cheaper chain.

Instructions

Compare what the same purchase (amount in yen before tax) costs at each chain after the CouponJP coupon and the tax refund fee. Answers 'is a drugstore, department store or duty-free shop cheaper?'.

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

Input Schema

NameRequiredDescriptionDefault
languageNoen
amount_jpyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish this as a safe, idempotent, read-only, open-world operation, so the bar is lower. The description adds real behavioral content by stating the comparison is computed after the CouponJP coupon and the tax refund fee, but it leaves ambiguous whether the tax refund fee is deducted or added, which coupon variant applies, and what the comparison result looks like.

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?

Two sentences with the core purpose front-loaded and no filler. The question-format second sentence is mildly redundant with the first but earns its place by concretizing the use case.

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

Completeness2/5

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

There is no output schema, so the description should indicate what comes back (per-chain totals, a cheapest option, savings amount), and it does not. Combined with unspecified coupon assumptions and an undocumented language parameter, an agent can guess the intent but not the result shape or constraints.

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 must carry parameter meaning. It usefully clarifies that amount_jpy is the pre-tax yen amount, which the schema does not say, but the language parameter is never mentioned and no defaults, ranges, or valid values are discussed.

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?

Specific verb plus resource: compares the cost of the same pre-tax yen purchase across chains after a named coupon and tax refund fee, and frames the question it answers (drugstore vs department store vs duty-free). It is clearly a cost-comparison tool rather than a lookup like find_coupon_stores or tax_free_guide, though it never names a sibling 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?

The closing question 'is a drugstore, department store or duty-free shop cheaper?' implies the scenario for calling it, but there is no explicit when-to-use versus when-not, no statement of prerequisites (which coupon, eligibility for tax refund), and no routing to alternatives.

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