hive

by cmgmyr

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

kv_set

Destructive

Set a small shared JSON value other sessions can discover, with an optional TTL in seconds.

Instructions

Set a small shared JSON value other sessions can discover. Optional TTL in seconds.

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": "kv_set"
  }
}

Input Schema

Name	Required	Description
`key`	Yes
`value`	Yes	Any JSON value.
`project_id`	No	Different project override. Use ONLY when the user explicitly asks for another project by name; otherwise stay in the current scope, even when results are empty.
`ttl_seconds`	No

Output Schema

Name	Required	Description	Default
`key`	Yes
`project_id`	Yes
`hive_notice`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.2.2Sep 26, 2026
- addedOutput schema / properties / hive_notice
```
Added value: +{
+  "type": "string"
+}
```
First observedv1.0.0Sep 22, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, destructive write (overwrites), so the safety picture is partially covered. The description usefully adds cross-session visibility and TTL semantics, but does not clarify overwrite behavior, the meaning of 'small', or any key/value limits despite destructiveHint.

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?

Two short sentences, front-loaded with the core action and followed by the optional modifier. No filler.

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?

Output schema exists and annotations cover the destructive/overwrite profile, so the description need not explain returns. Still, for a cross-session shared-value write tool it omits overwrite semantics and 'small' size expectations, leaving notable gaps.

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 50%; project_id is well documented in the schema while key and ttl_seconds are not. The description adds the unit for ttl_seconds ('in seconds'), a real gain, but says nothing about key naming rules or project scoping beyond what the schema provides.

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+resource ('Set a small shared JSON value') with scope info ('other sessions can discover'), clearly distinct from kv_get/kv_delete by name and semantics. No explicit sibling differentiation, but the resource is unambiguous.

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 phrase 'other sessions can discover' hints at the cross-session sharing use case, but there is no explicit when-to-use, when-not, or reference to alternative tools. The agent must infer usage entirely from the name and sibling list.

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