Skip to main content
Glama

EchoRelay

by dev.echorelay
OverviewDiscussionsAdmin

rollback_config

Destructive

Preview or apply publishing a retained line revision over what is currently published, clearing any pending schedule. Without confirmRevision this only returns the diff (the redacted change-gate preview, same shape as config_diff) between what is currently published and the target revision — it changes nothing. To apply, call again with confirmRevision set to the diff's currentRevision; if a publish landed since the preview, confirmRevision is now stale and the call is refused with error "rollback_confirmation_conflict" instead of silently overwriting the newer publish — read the fresh diff and confirm again. Applying also requires confirmUnsigned, the preview's unsignedFingerprint, so a signing secret expiring between the preview and the confirm cannot roll a target back unsigned without you having seen it named.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lineKeyYes
revisionYes
confirmRevisionNoThe currently-published revision number from the preview diff. Omit to preview only; include to apply.
confirmUnsignedNoThe preview diff's unsignedFingerprint. Required whenever confirmRevision is given: a target's retained signing secret expires on a clock, so this proves the confirm saw the same set of targets the preview named as coming back unsigned. A stale one is refused with "rollback_confirmation_conflict".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirmUnsigned
      Added value: +{
+  "description": "The preview diff's unsignedFingerprint. Required whenever confirmRevision is given: a target's retained signing secret expires on a clock, so this proves the confirm saw the same set of targets the preview named as coming back unsigned. A stale one is refused with \"rollback_confirmation_conflict\".",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / confirmRevision
      Added value: +{
+  "description": "The currently-published revision number from the preview diff. Omit to preview only; include to apply.",
+  "minimum": 1,
+  "type": "integer"
+}
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=true, while the description adds substantial context: it clears any pending schedule, the preview changes nothing, a stale confirm is refused with rollback_confirmation_conflict rather than silently overwriting a newer publish, and confirmUnsigned guards against a signing secret expiring between preview and confirm.

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?

Dense and front-loaded, leading with what the tool does and when it changes nothing. Several clauses (redacted change-gate preview, the signing-secret rationale) are lengthy, so it is informative but not maximally tight.

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

Completeness5/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 carries the return-value burden and does so by explaining that the preview returns a diff shaped like config_diff, plus the exact error code on conflict. For a destructive, confirmation-gated mutation this is complete enough to call safely.

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?

Schema coverage is 50%, and the description adds real meaning for the two confirm parameters, including their source fields (currentRevision, unsignedFingerprint) and the failure mode of each. However, lineKey and revision are left entirely unexplained in both the schema and the description.

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

Purpose5/5

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

States a specific verb and resource: previewing or applying a retained line revision over the currently published config. It explicitly differentiates itself from siblings by naming config_diff as the shape the preview matches and by describing the publish-overwrite semantics that distinguish it from publish_line_draft.

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

Usage Guidelines5/5

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

Gives an explicit two-step protocol: call without confirmRevision to preview only, call again with confirmRevision equal to the diff's currentRevision to apply. It also states the when-not condition (stale confirmation is refused) and the additional confirmUnsigned prerequisite.

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

All EchoRelay toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources