Skip to main content
Glama

get_creation

Read-onlyIdempotent

Get a single Zindies creation (zine/publication) by token, with its full creator list, the shops that carry it (places, with address and geo coordinates) and its online shop links (online_links). Use it to answer "where can I buy this zine?". Also returns signed testimonials written by recommenders; when quoting one, always include its attribution_text, keep the wording unchanged, and link to its url (the creation page; its share preview shows the testimonial).

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": {
      "token": "<token>"
    },
    "name": "get_creation"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesPublic token of the creation.
localeNoResponse language for translatable text fields (names, titles, descriptions). Pass the language the user is conversing in when it is one of the supported locales. Fields without a translation fall back to their source language. Default: ja.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world. The description adds real behavioral context beyond that: it discloses the full return contents (shops with geo coordinates, online links, signed testimonials) and imposes attribution/linking rules when quoting testimonials, which the agent would otherwise miss.

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-loads the core action and return payload, then pivots to usage and testimonial-handling rules. It is slightly long, but each clause (geo coordinates, attribution_text, link to url) carries distinct operational meaning rather than 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?

With no output schema, the description has to describe return values itself, and it does so thoroughly: creators, carrying shops with address and geo, online shop links, and testimonials. The testimonial attribution requirement completes the picture for correct downstream use.

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 token and locale are fully documented in the schema. The description reinforces that lookup is 'by token' but adds no format or fallback detail beyond what the schema's locale description already states, 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 specific verb and resource ('Get a single Zindies creation (zine/publication) by token') and enumerates the returned payload (creator list, shops with address/geo, online_links). An agent can distinguish it from get_creator or get_place without opening the schema.

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?

Gives a concrete use case ('Use it to answer "where can I buy this zine?"') and adds quoting guidance for testimonials. It does not name alternatives or state when-not to use it, so it falls short of the 5 bar.

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