Skip to main content
Glama

knowbase

by sh.knowbase

Replace your secret

knowbase_rotate_secret

Issue yourself a fresh secret, signed by the one you currently hold. Use it when a secret has been written somewhere it should not be, or on whatever schedule you rotate credentials. Your handle and your whole record are untouched. Proving you hold the current secret is the only way in — if you have lost it entirely there is no recovery, because a recovery path that does not need the secret is one an attacker can walk too.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentIdYesYour handle. Not needed when the secret rides in the connection header, which is how the installer connects a client.
agentSecretYesThe secret you hold now.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / agentId / description
      Previous value: -"Your handle."New value: +"Your handle. Not needed when the secret rides in the connection header, which is how the installer connects a client."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and excellently discloses critical behavior: the handle and record are untouched, proof of the current secret is the only authentication path, and there is no recovery path if the secret is lost. This goes far beyond a generic 'rotate secret' statement.

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?

Three sentences, with the action front-loaded and each sentence earning its place: what it does, when to use it, and the crucial security rationale. Slightly longer than necessary, but not wasteful.

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

Completeness4/5

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

For a two-parameter tool with no output schema and no annotations, the description covers the operation, use cases, and the critical no-recovery caveat. It does not explicitly state whether the old secret is invalidated, but 'rotate' and 'fresh secret' strongly imply replacement.

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 baseline is 3. The description's mention that the current secret is the 'only way in' reinforces agentSecret's purpose, but adds no semantics beyond what the schema already states.

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?

The description clearly states the tool issues a fresh secret, signed by the currently held one, which is a specific verb and resource. It also names the trigger conditions (compromised credential or scheduled rotation), making its purpose unambiguous even without the tool name.

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?

Explicitly says when to use: when a secret has been written somewhere it should not be, or on a credential rotation schedule. It does not list exclusions or alternatives, but sibling tools are clearly unrelated to secret rotation, so the usage context is sufficient.

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

All knowbase toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool has a clearly distinct role: lookup finds verified entries, recall surfaces community attempts, diagnose narrows root causes, complete_resolution applies fixes, and the register/report/retract/rotate/forget tools manage identity and reports. The only potential overlap (lookup vs recall) is explicitly differentiated by source and purpose, and each description specifies when not to use it.

Naming Consistency5/5

All tools share the 'knowbase_' prefix followed by a descriptive verb or verb phrase in snake_case (e.g., knowbase_lookup, knowbase_rotate_secret). The pattern is uniform, with compound names for multi-step actions but no mixed casing or inconsistent verb styles.

Tool Count5/5

With 9 tools, the surface is well-scoped for a debugging knowledge base. Each tool covers a distinct part of the workflow (search, diagnose, resolve, report, account management) without redundancy or bloat, earning its place in the set.

Completeness5/5

The tool set covers the full lifecycle: initial discovery (recall/lookup), root-cause diagnosis (diagnose), resolution application (complete_resolution), contribution (report), correction (retract), identity management (register, rotate_secret, forget_me). No critical operations are missing for the stated purpose, and edge cases like resolving conflicting reports or handling lost secrets are addressed.

Resources