Skip to main content
Glama

Receive stay purchase proof

claim_stay_proof

Receive a stay purchase proof (SB-… ID, from a stay booked and paid through a GYOTAKU Protocol store window) with its claim code, and link it to your GYOTAK referral account. Works only through your personal token URL. Optional: show_referral puts your referral URL for that stay on the public proof page; handle links your own X account to the proof on the public chain (permanent; it cannot be removed). Call again with the same code to change show_referral or add an X account.

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": {
      "purchase_id": "<purchase_id>",
      "claim_code": "<claim_code>"
    },
    "name": "claim_stay_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNoYour own X handle without @ (optional; recorded permanently on the public chain). Pass it only if the user explicitly asks.
claim_codeYesClaim code shown with the booking status (SC-...)
purchase_idYesStay purchase proof ID, SB-YYYYMMDD-xxxxxxxx
show_referralNoShow your referral URL for this stay on the public proof page (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the things an agent most needs before mutating public state: the handle link is permanent and cannot be removed from the public chain, show_referral publishes the referral URL publicly, and access is scoped to a personal token URL. The re-call behavior is consistent with idempotentHint=false (repeat calls add state), so nothing contradicts the 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?

The core action and the token-URL constraint are front-loaded, and the optional-parameter behavior follows. It is dense with parentheticals and the final sentence could be merged, but no sentence is wasted.

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 mutating, open-world tool with no output schema, the definition covers auth requirement, public visibility, irreversibility, and repeat-call semantics. It leaves open what a claim code can't be reused for and what happens when the code or purchase ID is invalid, which matters for a state-changing call.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining the observable consequence of each optional parameter (show_referral publishes to the proof page; handle ties the X account permanently to the public chain) and by framing the same-code call as the way to modify them. That adds workflow meaning the schema fields alone do not convey.

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 gives a specific verb and resource ('Receive a stay purchase proof ... and link it to your GYOTAK referral account') and qualifies the resource with the SB- ID format and the GYOTAKU store-window origin, which distinguishes it from a generic proof tool. It does not name the sibling claim_purchase_proof, so the agent must infer the stay-vs-other distinction rather than being told directly.

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 states the operating prerequisite ('Works only through your personal token URL') and gives explicit re-invocation guidance ('Call again with the same code to change show_referral or add an X account'), which tells the agent this is the update path too. It stops short of naming when to prefer claim_purchase_proof instead, so the sibling routing is left implicit.

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