GYOTAK Fish Market

Share post kit

get_share_kit

Get the facts and constraints for writing a social media post about GYOTAK with the caller's referral URL: order facts, fish photo URLs, verification page URLs of the caller's stamped purchase proofs, allowed and forbidden claims, and the required referral disclosure. The wording is up to the user and their assistant. Call this again each time the user asks for a post; do not reuse a previous result.

Input Schema

Name	Required	Description	Default
`customerKey`	No	Your customerKey (gyotak_cus_...). Omit when connected through a personal token URL.
`includePhotos`	No	Set true only if the user wants to attach a photo they take themselves with a blockchain capture record. Returns photo_capture_url and the list of recorded photos.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

addedInput schema / properties / includePhotos

Added value: +{
+  "description": "Set true only if the user wants to attach a photo they take themselves with a blockchain capture record. Returns photo_capture_url and the list of recorded photos.",
+  "type": "boolean"
+}

AddedSep 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The annotations declare readOnlyHint=false and idempotentHint=false; the description explains the non-idempotency (re-fetch every time, never reuse) and clarifies that the tool supplies facts/constraints while the actual wording is left to the user. It does not explain why the operation is flagged as non-read-only (does it register or generate something server-side), which is the remaining behavioral gap.

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?

Three tight sentences with the returned payload front-loaded and the refresh constraint at the end. "The wording is up to the user and their assistant" earns its place by scoping what the tool does not do, though the sentence could be folded more tersely.

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?

With no output schema, the description carries the burden of describing the return payload and does so explicitly. It is complete enough to call correctly, with the only soft spot being the unexplained non-read-only annotation flag for a 'get' tool.

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 100%, so both customerKey and includePhotos are already documented in the schema, including the personal-token omission case. The description mentions the caller's referral URL and photo URLs but adds no syntax or usage detail for the parameters themselves; 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?

States a specific verb and resource (get the share kit) and enumerates exactly what it returns: order facts, fish photo URLs, verification page URLs, allowed/forbidden claims, and the required referral disclosure. This clearly separates it from siblings like report_share, my_referrals, and get_order_history.

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?

"Call this again each time the user asks for a post; do not reuse a previous result" gives explicit freshness guidance and implicitly defines when not to use cached output. It does not name any sibling alternative (e.g., report_share for reporting a published post), so routing guidance is incomplete but the primary usage condition is clear.

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 tools Inspect

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

Need Help?