Skip to main content
Glama

GYOTAK Fish Market

by com.thaifishsashimicatalog
OverviewDiscussionsAdmin

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

TableJSON Schema
NameRequiredDescriptionDefault
customerKeyNoYour customerKey (gyotak_cus_...). Omit when connected through a personal token URL.
includePhotosNoSet 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.

  1. Changed1 schema field changed
    • 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"
+}
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It states outputs (facts, constraints, URLs) and implies a read-only operation via the verb 'get'. It also notes freshness requirements ('do not reuse'). However, it does not explicitly state side effects, authentication implications, or rate limits, leaving some ambiguity despite the 'get' implication.

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 a single, front-loaded sentence that efficiently lists the content types and ends with a clear usage directive. It is concise with no fluff, though it is a bit long in enumerating items. Overall, it is well-structured and to the point.

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

Completeness3/5

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

There is no output schema or annotations, so the description must stand alone. It lists the categories of returned data (order facts, photo URLs, verification URLs, claims, disclosure) but does not detail the structure or format of the response. Given the complexity of the output, this is a moderate gap, but the list provides enough orientation for an agent to use the result.

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 baseline is 3. The description mentions photo URLs and referral URL, which loosely relate to includePhotos and customerKey, but does not add new meaning beyond the schema. The schema already explains both parameters effectively, so the description provides no extra value.

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 clearly states the tool fetches facts and constraints for writing a social media post about GYOTAK, listing specific deliverables (order facts, photo URLs, verification page URLs, allowed/forbidden claims, referral disclosure). This makes it distinct from siblings like apply_referrer or report_share, which serve different purposes.

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?

The description explicitly instructs to call the tool each time the user asks for a post and not to reuse previous results, providing clear when-to-use guidance. It also clarifies that wording is left to the user/assistant, setting scope. However, it does not name alternative tools or give when-not-to-use conditions, but the directive is strong.

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