Skip to main content
Glama
I4cTime

q-ring

by I4cTime
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

entangle_secrets

Idempotent

Link two secret keys so writes or rotations of either propagate to the other, preventing drift when one credential is stored under multiple names across scopes.

Instructions

[secrets] Link two keys (across the same or different scopes) so future writes/rotations of either propagate the same value to the other. Use when one logical credential lives under multiple names (e.g. STRIPE_SECRET_KEY global and project) and should never drift; prefer set_secret for unrelated values, and reverse the link with disentangle_secrets (does not delete values). Mutates only the metadata of both envelopes — the values themselves are not changed by this call. Idempotent: re-running on an already-entangled pair is a no-op. Subject to tool policy. Returns a short confirmation: 'Entangled: SOURCE <-> TARGET'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceKeyYesFirst secret key in the pair. Example: 'STRIPE_SECRET_KEY'.
targetKeyYesSecond secret key to keep in lockstep with the source.
sourceScopeNoWhere the secret lives. 'global' = user keyring (default if omitted on reads), 'project' = scoped to projectPath, 'team' = team-shared (needs teamId), 'org' = org-shared (needs orgId).global
targetScopeNoWhere the secret lives. 'global' = user keyring (default if omitted on reads), 'project' = scoped to projectPath, 'team' = team-shared (needs teamId), 'org' = org-shared (needs orgId).global
sourceProjectPathNoProject root for sourceKey when sourceScope='project'. Defaults to the server cwd.
targetProjectPathNoProject root for targetKey when targetScope='project'. Defaults to the server cwd.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.11.7
    • changedInput schema / properties / sourceKey / description
      Previous value: -"Source secret key"New value: +"First secret key in the pair. Example: 'STRIPE_SECRET_KEY'."
    • addedInput schema / properties / sourceProjectPath / description
      Added value: +"Project root for sourceKey when sourceScope='project'. Defaults to the server cwd."
    • changedInput schema / properties / sourceScope / description
      Previous value: -"Scope: global, project, team, or org"New value: +"Where the secret lives. 'global' = user keyring (default if omitted on reads), 'project' = scoped to projectPath, 'team' = team-shared (needs teamId), 'org' = org-shared (needs orgId)."
    • changedInput schema / properties / targetKey / description
      Previous value: -"Target secret key"New value: +"Second secret key to keep in lockstep with the source."
    • addedInput schema / properties / targetProjectPath / description
      Added value: +"Project root for targetKey when targetScope='project'. Defaults to the server cwd."
    • changedInput schema / properties / targetScope / description
      Previous value: -"Scope: global, project, team, or org"New value: +"Where the secret lives. 'global' = user keyring (default if omitted on reads), 'project' = scoped to projectPath, 'team' = team-shared (needs teamId), 'org' = org-shared (needs orgId)."
  2. Changed4 schema fields changedv0.11.5
    • changedInput schema / properties / sourceScope / description
      Previous value: -"Scope: global or project"New value: +"Scope: global, project, team, or org"
    • changedInput schema / properties / sourceScope / enum
      Previous value: -[
-  "global",
-  "project"
-]New value: +[
+  "global",
+  "project",
+  "team",
+  "org"
+]
    • changedInput schema / properties / targetScope / description
      Previous value: -"Scope: global or project"New value: +"Scope: global, project, team, or org"
    • changedInput schema / properties / targetScope / enum
      Previous value: -[
-  "global",
-  "project"
-]New value: +[
+  "global",
+  "project",
+  "team",
+  "org"
+]
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare idempotentHint, destructiveHint=false, and readOnlyHint=false, but the description adds meaningful non-structured context: it mutates only envelope metadata (values untouched), is subject to tool policy, and returns a specific confirmation string. The idempotency claim duplicates the annotation rather than extending it, keeping this just below a top score.

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?

The core action and routing guidance are front-loaded, and most sentences earn their place. Slightly dense with multiple parenthetical asides, but nothing is wasteful.

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?

Despite no output schema, the description states the return value explicitly, covers mutation scope, idempotency, and the sibling-based reversal path. An agent has everything needed to invoke it 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 all six parameters are already documented in the schema, including scope semantics and projectPath defaults. The description adds no new parameter-level detail, so the baseline 3 applies.

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 ('Link two keys') and clarifies scope ('across the same or different scopes') plus the propagation semantics. An agent can immediately distinguish this from set_secret and disentangle_secrets, which are named directly.

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?

Explicitly states when to use it (one logical credential under multiple names that should never drift), names the preferred alternative for unrelated values (set_secret), and points to the reverse operation (disentangle_secrets) with the note that it does not delete values.

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