Skip to main content
Glama

Record commitments

get_record_commitments
Read-only

The nightly Merkle roots that commit every settled call on this lane, with their on-chain attestations, newest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many days of roots (default 7).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 real behavioral context beyond that: nightly cadence, newest-first ordering, inclusion of on-chain attestations, and lane scoping. It does not mention pagination, retention, or rate/latency considerations, so it stops short of a 4.

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 tight sentence with no filler; the most distinguishing attributes (nightly, settled calls, attestations, newest first) are packed in without redundancy.

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

Completeness4/5

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

For a read-only lookup with zero required parameters and no output schema, the description usefully states what is returned (roots with attestations) and in what order, which substitutes for the missing output schema. Minor gaps—nothing about the 30-day cap or windowed retrieval—keep it from a 5.

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 100% and the single 'limit' parameter is fully documented as days of roots with a default of 7. The description adds nothing about the parameter, but the baseline of 3 applies when the schema carries the parameter semantics.

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 names a concrete resource—nightly Merkle roots committing every settled call on this lane, plus their on-chain attestations—so an agent knows exactly what data comes back. It lacks an explicit retrieval verb (no 'list' or 'fetch'), but the noun phrase is specific enough to distinguish it from every sibling (profile, offer, markets, agent search).

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?

It offers no when-to-use guidance, no prerequisites, and no alternatives or exclusions. The phrase 'on this lane' implies a lane-scoped context but never explains when an agent should reach for this tool versus other record or market queries.

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.

Resources