Skip to main content
Glama
Sign In
agent-governance MCP server

agent-governance MCP server

by Geomanti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

read_audit_log

Retrieve this run's decision audit log to inspect governance decisions and verify which tool calls were permitted or withheld.

Instructions

Read this run's decision audit log.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Read' implies a safe read-only operation and 'this run's' implies scoping, but it says nothing about authorization, what decisions are recorded, ordering, or size; it relies on the output schema to convey content.

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?

A single, front-loaded sentence with no filler. For a zero-parameter tool with an output schema, this is an appropriately sized description.

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?

The output schema covers return values, and there are no parameters to explain, so the core is adequate. However, the key term 'this run' is undefined and there is no link to sibling tools that read related artifacts, leaving the agent without context for when this log is relevant.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and there is no parameter semantics to document. Nothing in the description is needed or missing on this dimension.

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 gives a specific verb (read) and resource (decision audit log) and scopes it to 'this run'. It distinguishes the artifact from siblings like read_digest and read_ledger reasonably well, though 'decision audit log' vs 'ledger' overlap enough that an agent may still hesitate.

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?

There is no indication of when to read this log versus read_ledger or read_digest, nor any stated trigger or exclusion. The agent is left to infer the use case entirely.

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