Skip to main content
Glama
Sign In
keymaster-mcp

keymaster-mcp

by kiraa06
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

audit_log

Read-only

Review recent vault activity to see who revealed, used, or changed credentials and when, optionally filtered to one credential.

Instructions

Recent vault activity (who revealed/used/changed what, when). Optionally for one credential.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "audit_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the content of the log (actor/action/timestamp), but says nothing about ordering, pagination, or what 'recent' means in practice.

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?

One short parenthetical sentence, front-loaded with the resource and immediately followed by the optional filter. No filler.

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

Completeness3/5

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

For a simple read-only tool with no output schema and zero required parameters, the description is adequate but leaves the two parameters (ref format, limit semantics) and the log's ordering/unbounded-history behavior unaddressed.

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 0%, so the description carries the burden. It clarifies that 'ref' is optional and scopes the log to a single credential, but never defines the accepted ref format (id vs name) and ignores 'limit' and its default of 30 entirely.

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

Purpose4/5

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

Names a specific resource and scope: recent vault activity with the categories of events (revealed/used/changed) and the temporal frame (when). An agent can tell this is an activity feed, distinct from credential_history or list_credentials, though the relation to credential_history is not spelled out.

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

Usage Guidelines3/5

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

The phrase 'Optionally for one credential' implies the unfiltered-by-default behavior and the filter case, but it never states when to prefer this over credential_history or how far back 'recent' reaches.

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