Skip to main content
Glama
I4cTime

q-ring

by I4cTime
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tunnel_create

Stash a one-shot or short-lived secret in q-ring's process memory and return an ID for later reading, so one-time values can be shared without persisting them to disk.

Instructions

[tunnel] Stash a one-shot or short-lived secret in the q-ring server's process memory and return an ID that can be used to read it back. Use for handing a one-time value to another tool/process without persisting it (npm OTP codes, magic-link tokens, copy/paste between machines via a relay); prefer set_secret with ttlSeconds when you actually want a tracked, auditable secret. Mutates only in-memory state — the value never touches disk and is lost on server restart. Subject to tool policy. Returns JSON { ok, data: { id } } where id is an opaque string to pass to tunnel_read/tunnel_destroy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesThe plaintext value to tunnel. Held only in process memory; never logged.
maxReadsNoSelf-destruct after this many successful `tunnel_read` calls. Use 1 for true one-shot delivery.
ttlSecondsNoAuto-destroy the tunnel after this many seconds. Omit for no time limit (then a `maxReads` is highly recommended).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.11.7
    • changedInput schema / properties / maxReads / description
      Previous value: -"Self-destruct after N reads"New value: +"Self-destruct after this many successful `tunnel_read` calls. Use 1 for true one-shot delivery."
    • changedInput schema / properties / ttlSeconds / description
      Previous value: -"Auto-expire after N seconds"New value: +"Auto-destroy the tunnel after this many seconds. Omit for no time limit (then a `maxReads` is highly recommended)."
    • changedInput schema / properties / value / description
      Previous value: -"The secret value"New value: +"The plaintext value to tunnel. Held only in process memory; never logged."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds genuinely non-obvious traits: values stay in process memory, never touch disk, are lost on restart, and creation is subject to tool policy. It also names the downstream tools (`tunnel_read`/`tunnel_destroy`) that consume the returned id.

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?

Front-loaded with purpose and scope, then usage, behavior, and return shape in a tight sequence with no filler. It is a single dense block rather than cleanly separated sentences/lines, which slightly hurts scannability for a six-part message.

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?

No output schema exists, and the description compensates by specifying the return shape (`{ ok, data: { id } }`) and the opaque-id contract for `tunnel_read`/`tunnel_destroy`. Combined with the in-memory-loss caveat and policy note, an agent has everything needed to call and follow up 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 description coverage is 100%, so the schema already documents `value`, `maxReads`, and `ttlSeconds` including their self-destruct semantics. The description adds only indirect guidance (mentioning `ttlSeconds` in the `set_secret` comparison and warning that omitting a TTL makes `maxReads` strongly advisable), which is useful but not deep parameter elaboration.

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?

States a specific verb and resource ('stash a one-shot or short-lived secret in the q-ring server's process memory') plus the concrete artifact returned ('an ID that can be used to read it back'). It explicitly contrasts itself with the sibling `set_secret`, so an agent can pick between them without opening schemas.

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

Usage Guidelines5/5

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

Gives concrete use cases (npm OTP codes, magic-link tokens, copy/paste relay) and an explicit routing rule: prefer `set_secret` with `ttlSeconds` when a tracked, auditable secret is wanted. This is a clear when-to-use and when-to-use-something-else statement.

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