Skip to main content
Glama

router_journal

Read-onlyIdempotent

Lists recent router configuration changes and shows full before/after details plus requests by ID, so you can review changes and use the ID for undo.

Instructions

This server's change journal: action=list (recent changes, with ids) or action=show id=... (full before/after and requests). Use the id with router_undo.

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

Input Schema

NameRequiredDescriptionDefault
idNo
limitNo
actionNolist
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds valuable non-annotation context about what each mode returns (ids vs. full before/after plus requests), which matters because there is no output schema. It does not mention that secrets may be unmasked, but the reveal parameter carries that in the schema.

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 dense sentence with parenthetical clarifications, front-loaded with the resource and immediately followed by the mode breakdown and the cross-tool handoff. No filler, though the parenthetical nesting makes it slightly harder to scan than a short bulleted structure would.

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?

For a five-parameter tool with no output schema, the description usefully characterizes return content and the id handoff to router_undo. It leaves gaps around limit/pagination behavior, the router parameter's scope, and what happens for an unknown id, which an agent would need before invoking confidently.

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?

With only 40% schema description coverage, the description compensates for the most important gap by explaining the semantics of the action enum values and how id is obtained and reused. It adds nothing about limit (default 20, no description anywhere), and router/reveal are only documented in the schema, so coverage remains partial.

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?

"This server's change journal" plus the two action modes gives a specific verb/resource pair and distinguishes the tool from sibling log-style tools by emphasizing change history with ids. It does not explicitly contrast with router_logs, so an agent must infer that difference from the name alone.

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

Usage Guidelines4/5

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

The description clearly states the two modes and their selection criteria: action=list for recent changes with ids, action=show with id=... for full before/after and requests. It also routes the agent forward by saying to use the id with router_undo, though it gives no exclusion guidance against router_logs or other diagnostic siblings.

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