AgentsID Guard

Official

by AgentsID-dev

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

secrets_history

Audit secret changes by viewing rotation history. Requires read permission.

Instructions

View rotation history for a secret. Requires secrets.read.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Secret name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the auth requirement ('Requires secrets.read') which implies a read-only operation, but does not describe the return format, pagination, or any other behavioral effects. The description offers minimal transparency.

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?

The description is a single, front-loaded sentence that immediately states the purpose, followed by a concise permission note. There is no wasted information.

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

Completeness2/5

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

Despite the tool's simplicity (one parameter, no output schema), the description omits what the tool returns (e.g., list of rotations) and provides no usage context relative to sibling tools. The permission note is useful but insufficient for complete understanding.

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?

The input schema has a single parameter 'name' with a clear description ('Secret name'), achieving 100% coverage. The tool description adds no extra semantic meaning beyond the schema, so the baseline of 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?

The description clearly states 'View rotation history for a secret' with a specific verb and resource. This distinguishes it from sibling tools like secrets_list (list secrets) and secrets_audit (audit), as it specifically targets rotation history.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as secrets_audit or secrets_list. The only additional information is the permission requirement 'Requires secrets.read,' which is a prerequisite, not a usage guideline.

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