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

agent-governance MCP server

by Geomanti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

read_ledger

Retrieve the ledger of work absorbed per agent to track workload distribution, verify accountability, and see how tasks are allocated across agents.

Instructions

Read the ledger of work absorbed per agent.

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_ledger"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosure, and "Read" only weakly implies a safe, non-mutating operation. It says nothing about scope (whole ledger vs per-agent window), pagination, permissions, or how the ledger is populated, though the presence of an output schema covers the return shape.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity comes at the cost of the detail noted in other dimensions rather than being admirably compact.

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?

For a tool with no annotations, no parameters, and an output schema, the description still needs to convey scope and how it differs from read_audit_log/read_digest. It leaves both unaddressed, so an agent cannot confidently choose this tool over its siblings.

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 there is no parameter semantics to explain; the baseline for a parameterless tool applies. Nothing in the description contradicts the empty schema.

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

Purpose3/5

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

It states a verb (Read) and a resource (ledger of work absorbed per agent), which is more than a tautology, but "work absorbed" is unexplained jargon. It also fails to distinguish itself from sibling read_audit_log or read_digest, which sound like the same kind of read-report operation.

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 use this tool rather than read_audit_log or read_digest, nor any prerequisite or context for calling it. The agent must guess based on the name alone.

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