Skip to main content
Glama

list_apps

Read-onlyIdempotent

List the free, no-sign-up tools Zindies offers under zindies.co/apps/ (not data Zindies holds about creators / shops / events). Use this when the user wants to make a small ZINE by hand (a printable fold-up template) or wants an image of a shop's monthly opening days for Instagram.

  • orizine: a printable template that turns one A4 sheet, cut and folded, into an 8-page A7 mini book. files lists every public PDF (pattern / page numbers / binding) with a direct pdf_url, and netprint when a Japanese convenience-store "Network Print" code is available for it (user_code, expires_at, qr_url; null when there is none right now). Codes are shared by everyone and are renewed before they expire, so always read them from this tool rather than reusing an old one. Print single-sided at 100% scale. The template is CC BY 4.0: credit Zindies; printing, handing out, adapting and selling the ZINEs made with it are free.

  • calendar: a web page that draws a month of opening days / closed days as a 1080x1350 PNG in the browser. It cannot be run through MCP: give the user url. If the shop is already registered on Zindies, its opening days are public data — use get_place (business_hours) instead of asking the user to re-enter them.

Each app carries next_step: how its output connects to Zindies (the signature printed on the output, registering as a creator / shop). Mention it once, quietly; do not push it.

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

Input Schema

NameRequiredDescriptionDefault
appNoReturn only this app. Default: all apps.
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.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description still adds substantial operational context: netprint codes are shared globally and renewed, so they must always be read fresh from this tool rather than reused; printing must be single-sided at 100% scale; the template is CC BY 4.0 with credit required but commercial use of the output permitted. These are behavioral facts an agent could not infer from structured fields.

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 scope statement is front-loaded and the per-app bullets are easy to scan, with no filler sentences. It runs long, but most of the length is compensating for the absent output schema by enumerating returned fields, so little of it is truly removable.

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 declared, the description carries the full burden of describing return shape and does so field by field, including null-handling for `netprint`. It also covers the cross-tool routing rule and a soft guidance note about `next_step`, leaving no obvious gap for correct invocation.

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

Parameters4/5

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

Schema coverage is 100% and both parameters are fully described, so the baseline is 3. The description goes further by explaining what each `app` enum value actually yields — `orizine` returns `files` with direct `pdf_url` values plus an optional `netprint` block (`user_code`, `expires_at`, `qr_url`), while `calendar` returns a page `url` — which meaningfully clarifies the enum beyond the schema's one-line default note.

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 opening line states a specific verb and resource ('List the free, no-sign-up tools Zindies offers under zindies.co/apps/') and immediately disambiguates from the sibling family by saying it is not 'data Zindies holds about creators / shops / events'. That contrast is exactly what separates it from get_place, list_events, and the other record-fetching siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names two concrete triggering intents (making a fold-up ZINE by hand, generating an Instagram image of a shop's monthly opening days) and an explicit when-not with the alternative: if the shop is registered, use get_place (business_hours) rather than asking the user to re-enter them. It also flags that `calendar` cannot be executed through MCP and only `url` should be handed back.

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