Skip to main content
Glama
kochetkov-ma

brewpage-mcp

by kochetkov-ma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

publish_kv

Creates a BrewPage key/value store entry addressed by namespace, id, and key, then returns its share link and owner token.

Instructions

Publish a key/value entry to BrewPage. Creates a KV store; the entry is addressed by (namespace, id, key). Repository defaults: 1 MiB per value, 1,000 keys per store. Returns its primary share link and owner token.

Input Schema

NameRequiredDescriptionDefault
keyYesKV key (first part of the (namespace, id, key) addressing tuple)
tagsNoOptional tags for the KV entry
valueYesKV value
ttlDaysNoRequested TTL: days as a number, or a string such as '2w', '36h' or '1 month' (default 15 days). The server rounds to whole days and clamps to the allowed range (1-30 by default; owner caps differ), reporting each adjustment in notices; use returned expiresAt.
passwordNoOptional password to protect the KV store
namespaceNoOptional. Omit to generate an unlisted namespace: anyone with its unpassworded link can read it, but it is excluded from gallery/search. Pass a custom namespace to group unlisted content, or pass `public` ONLY when the user explicitly wants gallery/search eligibility. Password-protected content stays excluded; unlisted, protected or otherwise ineligible native responses carry noindex; eligible public HTML, sites and files may permit indexing.
ownerTokenNoExisting owner token to group this KV store under the same owner as previous content
deliveryModeNoOptional delivery choice for a fresh publication, independent of password/namespace. Fresh sites and HTML-format pages outside public (including the default unlisted namespace) always use subdomain; an explicit path there still publishes, on subdomain, with a delivery notice. Everything else in any namespace (Markdown, code/text, files, JSON, KV, public HTML) defaults to path (Promotion); public HTML may automatically choose subdomain for browser features. When creation returns an existing publication, it keeps its actual mode and URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses quota defaults (1 MiB per value, 1,000 keys per store), that a KV store is created, and what is returned (primary share link and owner token). It omits overwrite/duplicate-key behavior and whether a create-side-effect occurs on repeated publishes, which keeps it from a 5.

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?

Three short sentences, front-loaded with the action and addressing, then limits, then return shape — every clause earns its place. Minor looseness in the "Repository defaults" phrasing, but no padding.

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 an 8-parameter mutation tool with no annotations and no output schema, the description supplies the return values, quotas and addressing model an agent needs. The remaining gap is whether publishing the same (namespace, id, key) creates a new store or updates an existing one, which materially affects correct invocation.

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 baseline is 3; every parameter including ttlDays clamping and deliveryMode is already documented in the schema. The description only adds the (namespace, id, key) tuple concept and quota defaults, which are useful but not parameter-level semantics beyond 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?

States a specific verb and resource ("Publish a key/value entry to BrewPage") and adds the addressing model (namespace, id, key), which is more than the name conveys. It does not differentiate against siblings such as set_kv, publish_json or publish_file, so an agent must infer which publish/set variant 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 Guidelines2/5

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

The description never says when to use this instead of set_kv, publish_json or publish_file, nor any prerequisite or exclusion. The only routing-like guidance (namespace unlisted vs public) lives in the schema's namespace parameter, not in the description itself.

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

Deploy Server

Other Tools