Fetch a stored value from a BrewPage KV store by namespace, ID, and key, including protected stores via password, to retrieve configuration or data for AI workflows.
Fetch a value from a BrewPage KV store by namespace, ID, and key.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | KV store ID | |
| key | Yes | Key to fetch | |
| password | No | Password if the KV store is protected | |
| namespace | Yes | KV store namespace |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so the description carries the full burden. It conveys only that this is a read, but says nothing about behavior when the key is missing (error vs null), authentication for protected stores, or any rate/size limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with zero waste. Nothing redundant, and the identifying parameters come before any qualifiers.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations, no output schema, and an optional password parameter, the description should explain what is returned and how protected stores behave. It leaves the return shape (raw string vs JSON value) and error conditions entirely undocumented.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already defines all four parameters including the optional password. The description merely echoes three of them and omits password, adding no meaning beyond the schema; baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb 'Fetch' plus resource 'value from a BrewPage KV store' and the identifying trio of namespace/ID/key. It is distinguishable from set_kv and publish_kv by the read verb, though no sibling is named explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus get_json, set_kv, or publish_kv, and no prerequisites stated (e.g., that a password is needed for protected stores). The agent must infer everything from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.