Skip to main content
Glama

Share post kit

get_share_kit
Destructive

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.

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

Input 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.9/5.0
Behavior3/5

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

The description does useful work beyond annotations by disclosing response contents and the freshness requirement, which dovetails with idempotentHint=false. However, annotations declare readOnlyHint=false and destructiveHint=true on a tool described purely as 'Get', and the description never reconciles that tension (e.g. whether prior kits/URLs are invalidated, whether anything is written). With annotations already carrying the safety profile, this is an adequate but incomplete disclosure.

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?

Front-loaded with the purpose, then the payload list, then the wording disclaimer and the freshness rule — a logical order with no filler. The middle enumeration is long but each item carries distinct information an agent needs, so the length is earned rather than padded.

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?

There is no output schema, and the description compensates well by naming the fields the agent will receive. The main residual gap is what to do after obtaining the kit (where the generated post goes), which matters for a tool whose sibling set includes a share-reporting 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 description coverage is 100%, so both parameters (customerKey and includePhotos) are already documented, including the omit rule for personal-token connections. The description's mention of photo URLs and verification page URLs loosely overlaps includePhotos but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 concrete verb ('Get') plus the exact resource: the facts and constraints for writing a social media post about GYOTAK with the caller's referral URL. It enumerates the payload (order facts, fish photo URLs, verification page URLs, allowed/forbidden claims, required referral disclosure) and explicitly scopes the tool as supplying material rather than wording, which separates it from a posting/reporting sibling.

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' is a clear, actionable usage rule with an explicit prohibition. It also clarifies the division of labor ('The wording is up to the user and their assistant'), implicitly steering post-submission elsewhere. It stops short of naming a specific alternative for actually publishing the post.

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