Skip to main content
Glama
Sign In
hydrate-dehydrate-mcp

hydrate-dehydrate-mcp

by slidingbox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Retrieve a secret

retrieve_secret
Destructive

Retrieve a secret stored on Slidingbox with a token, reading it exactly once. The token becomes invalid after the first successful read, and a second call returns nothing.

Instructions

Read a secret stored on Slidingbox, using the token from store_secret. This destroys it: the token is dead the instant this succeeds, and a second call returns nothing. Reading is paid (x402) unless an evaluation key is configured.

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": {
      "token": "<token>"
    },
    "name": "retrieve_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe sb_<pointer>#<key> token from store_secret.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Explicitly discloses the destructive nature ('token is dead... second call returns nothing'), aligning with destructiveHint=true. Adds payment/cost context and the evaluation key exception, which annotations do not cover.

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 sentences, front-loaded with purpose, then behavioral caveats. No redundant wording.

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

Completeness5/5

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

Covers purpose, prerequisites, one-time behavior, and cost. Since there is no output schema, the description implies the return is the secret itself, which is sufficient for a single-parameter tool.

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 already fully documents the token parameter with format and origin. Description reinforces the origin but adds no new semantic meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the action ('Read') and the resource ('secret stored on Slidingbox'), plus the token source. It distinguishes itself from siblings like store_secret by its read semantics, and from verify_endpoint by not mentioning verification.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Specifies the prerequisite of having a token from store_secret and warns about one-time use. It doesn't explicitly name alternatives or exclusions, but the context of token provenance and destruction is clear.

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