Skip to main content
Glama

Set KV value

set_kv
DestructiveIdempotent

Set a key of an existing KV store (create or replace); the key hosting is reserved.

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

Input Schema

NameRequiredDescriptionDefault
idYes
keyYes
valueYes
namespaceYes
ownerTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / id / description
      Removed value: -"KV store ID"
    • removedInput schema / properties / key / description
      Removed value: -"Key to set"
    • removedInput schema / properties / namespace / description
      Removed value: -"KV store namespace"
    • removedInput schema / properties / ownerToken / description
      Removed value: -"Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
    • removedInput schema / properties / value / description
      Removed value: -"Value to assign to the key"
  2. Changed1 schema field changed
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Owner token from create. Default: BREWPAGE_OWNER_TOKEN."New value: +"Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
  3. 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
  4. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=true, and destructive=true, so the safety profile is covered. The description adds genuine value by disclosing the overwrite behavior ("create or replace") and the reserved `hosting` key constraint, but says nothing about required permissions, the role of ownerToken, or limits on value size.

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

Conciseness5/5

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

A single tight sentence with the core action front-loaded and the reserved-key constraint appended efficiently. Nothing is wasted.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter mutating tool with zero schema coverage and no output schema, this is thin: the identity parameters (namespace, id) and the ownerToken auth parameter are undocumented, and there is no indication of return behavior or failure modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden, yet it only sheds light on `key` (the reserved `hosting` value) and implicitly `value`. The namespace, id, and especially ownerToken parameters get no explanation of format or auth implications.

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 ("Set a key of an existing KV store") and clarifies the create-or-replace semantics in parentheses. It does not distinguish itself from the sibling publish_kv, so an agent must infer the boundary.

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?

There is no explicit when-to-use guidance, no mention of when not to use it, and no reference to alternatives such as publish_kv. The only implied context is that the KV store must already exist, which is stated as a precondition rather than usage guidance.

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.