Skip to main content
Glama

Plures

List versions of the agent map

get_map_versions
Read-only

Lists the kept versions of an app's agent map, newest first: each new map of the code and each change to a check (added, turned off, edited, added by the team), with who and how many checks were on. Use it to find a version to restore.

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

Input Schema

NameRequiredDescriptionDefault
appNoThe app id. Default: PLURES_APP, then the default app
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful behavior detail — newest-first ordering, the contents of a version record, and the implicit fact that only 'kept' versions are returned (retention pruning). It says nothing about pagination behavior or what the limit default yields.

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?

One front-loaded sentence with a parenthetical enumerating version triggers, followed by a short usage clause. Mostly efficient, but the enumeration is slightly dense and repeats 'added' twice, which costs a bit of scanability.

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 read-only list tool with no output schema, the description covers what the tool returns (ordering, per-version metadata) and why to call it. The main omission is the limit parameter's behavior, which is left entirely to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: 'app' is documented in the schema (including its PLURES_APP fallback chain) while 'limit' has bounds but no description. The description mentions neither parameter, so it adds no meaning beyond the schema and leaves the undocumented limit parameter unexplained except for the oblique 'newest first' ordering hint.

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 ('Lists the kept versions of an app's agent map') plus ordering ('newest first') and what a version captures (new map of the code, check changes, who, check count). That clearly separates it from get_agent_map (current map) and restore_map_version, though no sibling is named explicitly.

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?

'Use it to find a version to restore' gives a concrete selection context that points the agent toward restore_map_version as the follow-up action. It lacks any explicit when-not guidance (e.g., use get_agent_map for the current map), but the intended use case is unambiguous.

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.