Skip to main content
Glama

Plures

Restore a version of the agent map

restore_map_version
Destructive

Makes an older version of an app's agent map current again, which checks are on and their routing included. It is saved as a new version, so it can be undone the same way. Changes which decisions go to people: confirm with the user first.

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": {
      "version": "<version>"
    },
    "name": "restore_map_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoThe app id. Default: PLURES_APP, then the default app
versionYesThe version to bring back, from get_map_versions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already flag destructive=true, idempotent=false and openWorld=true, and the description adds substantive context on top: the restore is written as a new version, so it can be undone the same way, and it alters human-decision routing. That reversibility mechanism and blast-radius disclosure are exactly the traits annotations cannot convey. It also gives the confirm-with-user instruction the destructive hint implies.

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?

Three short sentences, front-loaded with what the tool does, then the reversibility fact, then the caution. The final sentence's colon construction ('Changes which decisions go to people: confirm with the user first') is slightly compressed but still readable. No filler.

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 two-parameter mutation with no output schema, the description covers purpose, what the restored state contains, the undo path, and the human-approval caution. What is missing is what the caller gets back (e.g. a new version id) and whether the restore can fail on a stale version. Those are minor gaps given annotations and schema already cover safety and inputs.

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 coverage is 100%, so both the 'app' default chain and the 'version' parameter are already fully documented in the schema, including the pointer to get_map_versions. The description adds no format or edge-case detail (e.g. behavior for an invalid or already-current version). Baseline 3 is appropriate when the schema carries the parameter burden.

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?

States a specific verb and resource: making an older version of an app's agent map 'current again', and clarifies the scope of what is restored (which checks are on and their routing). This clearly distinguishes it from get_map_versions, which supplies the version number. It stops short of naming a sibling alternative explicitly, but the operation is unambiguous.

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?

Gives an explicit precondition for use: because it 'changes which decisions go to people', the caller should 'confirm with the user first'. That is actionable guidance beyond a bare description. It does not, however, state when-not to use it or name a comparison tool such as get_map_versions or submit_agent_map.

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.