Skip to main content
Glama

brochure_get

Read-onlyIdempotent

FREE, no key for a published page: one brochure as data (the blocks it shows, the prose, and every number read from its subject now: verdict, rung, record, windows, curve, venues, receipts). Its owner also gets the current draft, its versions, the file and anything to fix before publishing.

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": {
      "slug": "<slug>"
    },
    "name": "brochure_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesthe brochure's address
versionNoowner only: an older version

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses two things the annotations cannot: no API key is required for published pages, and the returned payload is conditional on ownership (owners additionally get the current draft, version history, the file, and a pre-publish fix list). Those auth and content-varies-by-caller traits are genuinely useful. It stops short of covering failure behavior for unpublished or nonexistent slugs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The access condition is correctly front-loaded ('FREE, no key for a published page'), but the long parenthetical inventory of returned fields is dense and largely a comma-separated jargon dump. The second sentence is doing real work by describing the owner view, but the field enumeration could be tightened considerably.

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?

With no output schema, the description carries the burden of describing the return value, and it does so by listing the payload sections for both the anonymous and owner cases. Combined with full annotation coverage and complete parameter documentation, an agent has enough to invoke it correctly. It is only slightly short on what happens when the slug is unpublished or the caller is unauthenticated.

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 'slug' and 'version' are already documented, and the schema already states that 'version' is owner-only. The description reinforces the public-versus-owner framing that governs those two parameters but adds no new syntax, format, or default information. Baseline 3 is appropriate when the schema carries the parameter detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes clear this returns 'one brochure as data' and enumerates what comes back (blocks, prose, computed numbers). It also distinguishes the public view from the owner view, which separates it from draft/list siblings. It loses a point because the verb is implicit and the payload is described in opaque domain jargon ('rung', 'curve', 'receipts') that a newcomer can't decode.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'for a published page' suggests the public fetch path, and 'its owner also gets...' implies an authenticated variant with extra fields. There is no explicit when-to-use/when-not guidance and no named alternative (e.g. brochure_draft or brochure_list) for cases where the caller wants only the draft or a collection rather than one published brochure.

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