Skip to main content
Glama

Publish KV entry

publish_kv

Create a KV store with its first entry (max 1 MiB per value, 1,000 keys); the key hosting is reserved. Returns the share link, the owner token and manageUrl (private: its holder can edit or delete). Owner tokens and management links never go into published content.

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": {
      "key": "<key>",
      "value": "<value>"
    },
    "name": "publish_kv"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
tagsNo
valueYes
ttlDaysNoDays to keep it: up to 30 days without an account, up to 90 with a free profile (an ownerToken held in the profile). Omitted: the default. The result states the expiry.
passwordNo
namespaceNoOmit (default): private. `public`: the shared public namespace. JSON and KV are never listed in the gallery or indexed; anyone with the link can open it. A custom name: 1-32 of a-z, 0-9, hyphen.
ownerTokenNoOwner token of an earlier create

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / deliveryMode
      Removed value: -{
      -  "description": "Optional 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.",
      -  "enum": [
      -    "path",
      -    "subdomain"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / key / description
      Removed value: -"KV key (first part of the (namespace, id, key) addressing tuple)"
    • changedInput schema / properties / namespace / description
      Previous value: -"Omit (default): private. namespace=public: the shared public namespace. JSON and KV are never listed in the gallery or indexed, in any namespace; anyone who has the link can open it. Lowercase only: 1-32 of a-z, 0-9, hyphen."New value: +"Omit (default): private. `public`: the shared public namespace. JSON and KV are never listed in the gallery or indexed; anyone with the link can open it. A custom name: 1-32 of a-z, 0-9, hyphen."
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Optional; the ownerToken from your first create keeps publications under one owner. Default: env BREWPAGE_OWNER_TOKEN (local server only), else a new token per create."New value: +"Owner token of an earlier create"
    • removedInput schema / properties / password / description
      Removed value: -"Optional password to protect the KV store"
    • removedInput schema / properties / tags / description
      Removed value: -"Optional tags for the KV entry"
    • removedInput schema / properties / ttlDays / anyOf
      Removed value: -[
      -  {
      -    "exclusiveMinimum": 0,
      -    "type": "number"
      -  },
      -  {
      -    "maxLength": 32,
      -    "minLength": 1,
      -    "type": "string"
      -  }
      -]
    • changedInput schema / properties / ttlDays / description
      Previous value: -"TTL in days: up to 30 days without an account, up to 90 with a free profile (pass an ownerToken held in the profile); a default applies when omitted. Accepts whole days: 15, '15d', '15 days'. The returned expiresAt is the actual expiry."New value: +"Days to keep it: up to 30 days without an account, up to 90 with a free profile (an ownerToken held in the profile). Omitted: the default. The result states the expiry."
    • addedInput schema / properties / ttlDays / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / ttlDays / type
      Added value: +"number"
    • removedInput schema / properties / value / description
      Removed value: -"KV value"
  2. Changed1 schema field changed
    • changedInput schema / properties / ttlDays / description
      Previous value: -"Requested 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; up to 90 with an owner token in a profile), reporting each adjustment in notices; the returned expiresAt is the actual expiry."New value: +"TTL in days: up to 30 days without an account, up to 90 with a free profile (pass an ownerToken held in the profile); a default applies when omitted. Accepts whole days: 15, '15d', '15 days'. The returned expiresAt is the actual expiry."
  3. Changed1 schema field changed
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Optional. Default: env BREWPAGE_OWNER_TOKEN (local server only), else a new token per create."New value: +"Optional; the ownerToken from your first create keeps publications under one owner. Default: env BREWPAGE_OWNER_TOKEN (local server only), else a new token per create."
  4. Changed1 schema field changed
    • changedInput schema / properties / ttlDays / description
      Previous value: -"Requested 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; the returned expiresAt is the actual expiry."New value: +"Requested 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; up to 90 with an owner token in a profile), reporting each adjustment in notices; the returned expiresAt is the actual expiry."
  5. Changed1 schema field changed
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Optional. Default: BREWPAGE_OWNER_TOKEN, else a new token per create."New value: +"Optional. Default: env BREWPAGE_OWNER_TOKEN (local server only), else a new token per create."
  6. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  7. Changed1 schema field changed
    • changedInput schema / properties / ttlDays / description
      Previous value: -"Requested 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."New value: +"Requested 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; the returned expiresAt is the actual expiry."
  8. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnlyHint=false/destructiveHint=false annotations, the description discloses hard quotas, a reserved key name, and the return payload (share link, owner token, manageUrl) with a clear warning that the owner token grants edit/delete rights and must not be published. That is meaningful behavioral context the annotations do not carry. It stops short of stating what happens on a key collision (fail vs. overwrite) or auth requirements.

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 dense sentences, front-loaded with the creation action and quotas, then closing on the security-critical token warning. Every clause carries information; the only cost is that the quota parenthetical slightly crowds the opening sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 usefully names the returned fields, and annotations cover the safety profile, so the basics are complete. However, for a 7-parameter mutation tool it leaves collision behavior, tags, and password undefined, which an agent may need before calling it correctly.

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 43%, so the description must compensate and it only partly does: it constrains `key` (reserved `hosting`) and `value` (1 MiB cap) and adds security context for `ownerToken`. The `tags` and `password` parameters have no explanation in either the schema or the description, leaving real gaps.

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 opens with a specific verb and resource: 'Create a KV store with its first entry,' which implicitly separates it from set_kv (adding entries to an existing store). It also states concrete limits (1 MiB per value, 1,000 keys) and a reserved key. It never names a sibling explicitly, so the differentiation is inferred rather than stated.

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?

The 'first entry' framing implies this is the creation path versus set_kv, but there is no explicit when-to-use or when-not-to-use guidance. Nothing tells the agent whether to use this versus publish_json or set_kv for a subsequent entry, leaving routing to inference.

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.