Skip to main content
Glama
Sign In
haver-governance-mcp

haver-governance-mcp

Official
by haverAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Get audit trail

get_audit_trail

Retrieve recent audit entries with optional filters by agent or resource to monitor governance actions.

Instructions

Return recent audit entries, optionally filtered by agent or resource.

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": "get_audit_trail"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
agent_idNo
resourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It indicates a read operation but lacks details on ordering, pagination, cost, or authentication requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no wasted words, but underspecifies important aspects. Acceptable conciseness but at the cost of completeness.

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?

No output schema, no annotations, and only 3 unrequired parameters. Description does not explain return format, default behavior, or any edge cases, making it insufficient for confident use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%. Description loosely maps agent_id and resource to filters but does not explain semantics, limits, or formatting. The limit parameter is not mentioned.

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?

The description clearly states the tool returns recent audit entries and can filter by agent or resource. It distinguishes from sibling tools like record_action or check_permission, but 'recent' is not quantified.

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 on when to use this tool versus alternatives like check_permission or verify_audit_integrity. No mention of prerequisites or context.

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