Skip to main content
Glama

Prior Ledger

ledger_head

Read-only

The newest entry's id, the entry count and the last 7 days of use. Anyone can verify the chain from the public repository.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds two useful behavioral facts beyond that — it returns the entry count and a 7-day usage window, and the chain is publicly verifiable — but it says nothing about the shape or limits of that 7-day figure or whether it is a summary versus raw records.

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?

Two short sentences with the substantive return information front-loaded. The public-repository sentence is slightly tangential but brief and justifies the tool's trust value, so it earns its place.

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?

With no output schema, the description must explain the return values, and it only does so loosely: 'last 7 days of use' and 'entry count' are not defined in terms of units, scope, or format. For a zero-parameter read this is close to sufficient, but an agent still cannot predict the response structure.

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 schema has nothing to explain and the baseline is 4. The description correctly implies no inputs are needed, consistent with the empty properties object.

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?

The description never uses a verb or names the resource; it lists what comes back ('the newest entry's id, the entry count and the last 7 days of use'). An agent can infer this is a ledger-head/status read, but it must infer the action rather than read it, and nothing distinguishes it from siblings like get_entry or list_subjects.

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 statement of when to call this versus get_entry, list_subjects, or search_precedent. Use is only implicitly suggested by the returned fields, leaving the agent to guess that this is a quick ledger-state check rather than a full entry fetch.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.