CallMCP — Phone Call MCP Server

List Agent Config Versions

list_config_versions

Read-onlyIdempotent

List the saved versions of an agent's settings, newest first: what saved each one (source), what changed (diff_summary), who (created_by) and which version a rollback came from. Secrets are never included. Pass version to fetch one version's full saved settings (config_snapshot). That snapshot holds the compiled prompt; to edit the prompt, read get_agent_config instead.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "list_config_versions"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max versions to return when listing (optional, default 50, max 100).
`version`	No	Fetch a single version by its per-agent version_number, including its redacted config_snapshot (optional; omit to list).
`agent_id`	Yes	Agent ID (required).

Output Schema

Name	Required	Description
`error`	No	Present when success is false
`success`	Yes	Whether the tool completed successfully
`version`	No
`agent_id`	No
`versions`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds real context beyond them: newest-first ordering, that secrets are never included, what the snapshot contains (compiled prompt), and what each row reports about provenance. It does not discuss pagination behavior for large version histories, which is the only notable gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core purpose, then the single-version mode, then the security note and the sibling redirect. No redundant or filler wording.

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?

An output schema exists, yet the description still supplies the key semantic context an agent needs: ordering, provenance fields, secret redaction, and the distinction between a list row and a full snapshot. Nothing material for correct invocation is missing.

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 100%, so the baseline is 3, but the description earns extra credit by explaining what `version` actually returns (the redacted config_snapshot and that it holds the compiled prompt) and by framing listing behavior that `limit` applies to. `limit` itself is left entirely to the schema.

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 ('List the saved versions of an agent's settings') plus ordering ('newest first') and the fields returned (source, diff_summary, created_by, rollback origin). It also distinguishes the two modes (list vs. single-version fetch) and explicitly points to get_agent_config for prompt editing, so it is separable from siblings.

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 explicit routing: omit `version` to list, pass `version` to fetch one full snapshot, and use get_agent_config instead when the goal is to edit the prompt. The conditions that select each path are stated rather than implied.

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

All CallMCP — Phone Call MCP Server tools Inspect

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.