Skip to main content
Glama

GYOTAK Fish Market

by com.thaifishsashimicatalog
OverviewDiscussionsAdmin

claim_purchase_proof

Claim the on-chain purchase proofs for your own purchases and attach your X (Twitter) handle to them, so a post of yours can be checked against the chain. Each stamped purchase comes with the URL of its public verification page. Only works through a personal token URL connector — there is no customerKey argument. Called with no arguments it only lists the purchases that can be claimed and claims nothing, every time — pass handle to actually claim. A claim is stamped on chain and cannot be undone, so let the user pick the handle before you pass one. The handle is what you tell us: GYOTAK does not verify that you own the account. Automatic binding of future purchases is off by default: to turn it on, pass handle with auto_bind "on" — the first such call returns the consent text; show it to the user word for word (the text is in Japanese and English; show both), and only if they agree call again with consent true. Pass auto_bind "off" to stop it (no handle needed); only later purchases stop, anything already recorded stays.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleNoYour X handle without the leading @ (letters, digits and underscore, 1-15 characters). Required to claim: a call without it only lists your purchases and claims nothing, even if you claimed before. Pass it on every claim.
consentNoSet true only when the user has read the consent text returned by an earlier auto_bind "on" call and agreed to it. Never set it on your own.
auto_bindNoTurn automatic binding of future purchases to your X handle on or off. "on" needs handle and consent. "off" needs nothing else. Omit to leave the setting as it is.
purchase_idNoClaim only this purchase (e.g. "PB-20260917-a97953d3"). Omit to claim every purchase of yours that is not claimed yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / auto_bind
      Added value: +{
+  "description": "Turn automatic binding of future purchases to your X handle on or off. \"on\" needs handle and consent. \"off\" needs nothing else. Omit to leave the setting as it is.",
+  "enum": [
+    "on",
+    "off"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / consent
      Added value: +{
+  "description": "Set true only when the user has read the consent text returned by an earlier auto_bind \"on\" call and agreed to it. Never set it on your own.",
+  "type": "boolean"
+}
  2. Changed2 schema fields changed
    • removedInput schema / properties / auto_bind
      Removed value: -{
-  "description": "Turn automatic binding of future purchases to your X handle on or off. \"on\" needs handle and consent. \"off\" needs nothing else. Omit to leave the setting as it is.",
-  "enum": [
-    "on",
-    "off"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / consent
      Removed value: -{
-  "description": "Set true only when the user has read the consent text returned by an earlier auto_bind \"on\" call and agreed to it. Never set it on your own.",
-  "type": "boolean"
-}
  3. Changed2 schema fields changed
    • addedInput schema / properties / auto_bind
      Added value: +{
+  "description": "Turn automatic binding of future purchases to your X handle on or off. \"on\" needs handle and consent. \"off\" needs nothing else. Omit to leave the setting as it is.",
+  "enum": [
+    "on",
+    "off"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / consent
      Added value: +{
+  "description": "Set true only when the user has read the consent text returned by an earlier auto_bind \"on\" call and agreed to it. Never set it on your own.",
+  "type": "boolean"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / handle / description
      Previous value: -"Your X handle without the leading @ (letters, digits and underscore, 1-15 characters). Required the first time; afterwards the handle from your last claim is reused unless you pass a new one."New value: +"Your X handle without the leading @ (letters, digits and underscore, 1-15 characters). Required to claim: a call without it only lists your purchases and claims nothing, even if you claimed before. Pass it on every claim."
  5. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly: claims are irreversible, GYOTAK does not verify handle ownership, no-arg calls claim nothing, auto_bind defaults to off, turning it off only affects future purchases, and consent text must be shown verbatim in both languages. There is no contradiction with annotations since none are provided.

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 description is long but dense and front-loaded, with the core purpose in the first sentence. Every clause covers a distinct behavioral rule or parameter interaction, and the consent/auto_bind flow justifies the length. It is not as compact as it could be, but there is no filler.

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?

For a stateful tool with no annotations and no output schema, this description covers the full call surface: list mode, claim mode, irreversibility, consent flow, auto_bind semantics, verification-page URLs, and the connector requirement. Nothing an agent needs to call it correctly or brief the user is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds crucial semantic context beyond the schema: handle is semantically required for claiming even though the schema marks it optional, consent must only be true after showing returned text, auto_bind 'on' requires handle and consent while 'off' requires neither, and purchase_id selects one claim vs all. This materially improves correct invocation.

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 opens with a specific verb and resource: 'Claim the on-chain purchase proofs for your own purchases and attach your X (Twitter) handle to them.' It clearly distinguishes this from verification-style siblings by focusing on claiming and stamping, and it explains the list-vs-claim duality. An agent can tell exactly what this tool does.

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 gives strong context: only works through a personal token URL connector, no customerKey argument, no-arg calls list only, handle required to actually claim, auto_bind consent flow, and off behavior. It does not explicitly name sibling alternatives or say 'use X instead,' so it stops just short of full when-not-to-use guidance.

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

All GYOTAK Fish Market toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources