Skip to main content
Glama

Read model alignment

ricursor_ledger
Read-only

Read scoped metadata and rule versions before switching models. Observe only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "ricursor_ledger"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject name inside the workspace.

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?

With readOnlyHint=true already declared, 'Observe only' mostly restates the annotation, though it usefully confirms no state changes occur. The description says nothing about what 'scoped' means beyond the required project, whether the ledger is cumulative, or how much history is returned.

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 action and scope front-loaded and the timing hint second. 'Observe only' is slightly redundant with the readOnlyHint annotation but is cheap reinforcement rather than clutter.

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?

A one-parameter read tool with annotations covering the safety profile and no output schema needs modest description support, which this largely meets. However, terms like 'ledger', 'alignment', and 'rule versions' are never grounded, so an agent cannot anticipate what it will receive or why it matters for a model switch.

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?

The single parameter has 100% schema description coverage, so the schema already establishes that project is a project name inside the workspace. The phrase 'scoped metadata' hints that the project acts as a scope key but adds no syntax or format detail.

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 supplies a specific verb and resource ('Read scoped metadata and rule versions') and adds a workflow purpose ('before switching models'). It does not distinguish itself from near-neighbours such as ricursor_context or ricursor_snapshot, so an agent cannot tell from the text alone which read tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Before switching models' gives a clear timing trigger for when to call it, which is more than nothing. There is no guidance on when not to use it and no named alternative for plain context or state reads, leaving sibling selection to inference.

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