Skip to main content
Glama

brochure_update

Change your brochure: send md (the whole cubicle.brand.md file) or patch (title, tagline, theme, tags, sections in order, off: the blocks switched off, prose: {hero, how, action}, update: {text} to post an update, price_usd and price_per for your own price; our fee is added from coord's margin) or restore (a version number). Every save is a version. Prose may not state a figure, a profit or a proof: the page draws those from the record. A published page keeps its published version until brochure_publish again.

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

Input Schema

NameRequiredDescriptionDefault
mdNothe whole file, frontmatter and ## blocks
slugYesthe brochure's address
patchNothe fields to change: {title, tagline, theme, tags, sections, off, prose: {hero, how, action}, update: {text, day?}, price_usd, price_per}
restoreNobring back this version

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?

Beyond the annotations (non-readOnly, non-idempotent), the description discloses that every save creates a version, that restore rolls back to a prior version, that published pages stay pinned until brochure_publish, that prose must not state figures/profit/proof because the page draws those from the record, and that a fee is added from coord's margin. These are substantive behavioral and validation facts an agent could not infer. It stops short of stating permissions or what the save returns.

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 purpose is front-loaded, and almost every clause carries information, but the whole definition is a single run-on sentence with deeply nested parentheses (patch, prose, update, pricing) that is hard to parse on first read. Structuring the three modes as separate statements would improve scanability without adding length.

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?

For a 4-parameter, nested-object mutation tool with no output schema, the description covers the modes, versioning, publish interaction, prose validation rule, and pricing behavior — enough to call it correctly. Gaps are the lack of any statement about what a save returns (no output schema exists) and no differentiation from the other brochure-editing siblings.

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 the schema already documents all four parameters; the baseline is 3. The description does add meaning the schema lacks — that md is the whole cubicle.brand.md file, that "off" switches blocks off, that update posts a text update, and how price_usd/price_per interact with coord's margin fee — but it restates much of the patch field list already present in the schema.

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?

"Change your brochure" pairs a clear verb with the resource, and the description enumerates the three write modes (md, patch, restore) so an agent can tell what kind of mutation is possible. It references brochure_publish for the publish lifecycle, but does not distinguish itself from siblings like brochure_draft or brochure_get, leaving some ambiguity about which editing tool to pick.

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?

Mode selection is spelled out: send md for a whole-file replacement, patch for field-level edits, restore for a version number. The note that "a published page keeps its published version until brochure_publish again" gives real context on when this tool's effect becomes visible. What is missing is explicit when-not guidance or a named alternative (e.g. brochure_draft) for draft work.

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