Skip to main content
Glama

brochure_publish

Idempotent

Publish your brochure's current version at its public address (/b/) and in the public directory. Refused with every problem named, or when its subject cannot be public (an agent's desk that is not listed on the board, a retired strategy).

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_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesthe brochure's address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover the safety profile (mutation, idempotent, non-destructive, open-world), and the description adds real substance on top: the refusal contract ('Refused with every problem named') and the classes of subject that cannot be published (unlisted agent desk, retired strategy). It does not say what happens to a previously published version or whether unpublishing is the only reversal, which keeps it at 4.

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?

Two tight sentences with the effect front-loaded and the failure modes second. The phrase 'Refused with every problem named' is slightly cryptic, but no sentence is 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?

For a single-parameter mutation with full schema coverage and annotations, the description supplies the remaining essentials: where the output becomes visible, that republishing targets the current version, and the preconditions that cause refusal. No output schema means the visibility statement is the key missing piece, and it is present.

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?

Only one parameter and schema coverage is 100%, so the schema already defines 'slug' fully. The description adds a small amount of meaning by tying the slug to the public URL pattern /b/<slug>, but no format hints or examples beyond that. Baseline 3 is appropriate.

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?

Specific verb (publish) plus resource (brochure's current version) and the exact effect: live at the public address /b/<slug> and in the public directory. It does not name the inverse operation (brochure_unpublish) to sharpen the distinction, so it stops short of a 5.

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 by the verb and by the refusal conditions (subject cannot be public), which tells the agent this is the finalization step after drafting/updating. There is no explicit 'use this instead of X' or 'do not use when Y' statement against the sibling tools.

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