Skip to main content
Glama

Thisispaper

by io.github.zaxarovcom
OverviewDiscussionsAdmin

List guides and editions

list_guides
Read-onlyIdempotent

Every hand-curated Thisispaper guide and edition. Guides are places: Tokyo, Kyoto, Lisbon, Copenhagen. Editions are themes: Black Matter (black as a way of handling light), Jutaku (Japanese houses on narrow plots), Icons, Off-the-Grid, Monographs on single architects. Returns each one's title, type, one-line description, cover image and public URL. Filter by city or by type. The full guides and editions are reserved for Thisispaper+ members.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoOptional city or region filter, e.g. 'tokyo' or 'portugal'. Applies to guides.
typeNoOptional: 'guide' for places, 'edition' for themes. Omit for both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"Optional city or region filter, e.g. 'tokyo' or 'portugal'."New value: +"Optional city or region filter, e.g. 'tokyo' or 'portugal'. Applies to guides."
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Optional: 'guide' for places, 'edition' for themes. Omit for both.",
+  "enum": [
+    "guide",
+    "edition"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so safety is clear. The description adds value by explaining the return fields (title, type, description, cover image, public URL) and the restriction that full guides/editions are for members, which is useful for agent decision-making.

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 well-structured and front-loaded with the main purpose, followed by content examples, return fields, and access caveat. Although it includes several examples, each sentence is informative and not wasted, though a slight trim could improve brevity.

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?

Without an output schema, the description adequately covers return fields, filtering, and access restrictions. It also enriches the context by explaining the difference between guides and editions, making the tool fully understandable in a single read alongside the annotations.

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 parameters are fully documented structurally. The description adds minimal extra meaning by mentioning 'Filter by city or by type' and clarifying that city applies to guides, but this does not significantly exceed what the schema already states.

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 'Lists' guides and editions, specifies the exact content (places like Tokyo, themes like Jutaku), and differentiates from siblings by focusing on a curated catalog. It names the resource and the action, making the purpose unambiguous.

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 implies when to use this tool: to fetch a list of all guides/editions with optional filters, and notes a membership restriction for full content. It does not explicitly contrast with sibling tools like 'discover' or 'search', but the intent is clear from the context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Thisispaper 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