Skip to main content
Glama

Buy (get checkout link)

buy
Read-onlyIdempotent

How to pay BokenJapan for a sponsorship tier or a Verified listing check. Returns the live Stripe Payment Link (hosted checkout the human buyer opens and pays on), price in JPY incl. and excl. 10% consumption tax, refund policy and legal disclosure links, and the bank-transfer invoice route. Does not take card data and does not charge anything: the buyer completes payment on Stripe. Call without product_id to list products. Product data comes from https://bokenjapan.com/pay.json.

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

Input Schema

NameRequiredDescriptionDefault
quantityNoVerified check: number of listings (one payment per listing). Sponsorship tiers: 1.
product_idNofounding | featured | regional | prefecture | addon | verified_check (ids from pay.json). Omit to list all products.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description still earns credit for the non-obvious behavioral fact that 'buy' performs no charge and handles no card data, with payment completed on Stripe — exactly the context an agent needs to avoid treating this as a purchase action. It also discloses what the response contains, though not its exact shape.

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?

Purpose and the crucial 'does not charge anything' clarification are front-loaded, followed by return contents and the listing mode. Sentences are dense but each carries information; only the pay.json URL sentence is arguably incidental.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing the return value and does so thoroughly: checkout link, tax-inclusive and tax-exclusive JPY prices, refund policy, legal disclosures, and bank-transfer route. For a two-parameter, zero-required read tool, nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so both product_id and quantity are already documented, including the 'omit to list all products' behavior. The description restates the listing mode and names pay.json as the id source, adding only marginal meaning beyond the schema. Baseline 3 is appropriate.

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?

The description names the concrete outcome — returning a live Stripe Payment Link for a sponsorship tier or Verified listing check — plus the ancillary payload (JPY price with/without 10% tax, refund policy, legal links, invoice route). The 'buy' name is ambiguous on its own, but the description immediately resolves it by stating nothing is charged. Siblings (get_listing, list_towns, search_places) cover an entirely different domain, so no further differentiation is needed.

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?

It explicitly states the alternate invocation mode: 'Call without product_id to list products.' That is a concrete when-to-use rule tied to a parameter state. It stops short of naming any sibling tool or exclusion condition, but the siblings are unrelated lookup tools, so the practical gap is small.

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