CallMCP — Phone Call MCP Server

Get Agent Change History

get_change_history

Read-onlyIdempotent

List an agent's recent config-change audit trail (change_type, change_source, old/new value, timestamp) — the same change log the owner hears when they call their line and ask what changed. Every change KaiCalls makes to an agent (via update_agent_config, configure_agent_business_rules, the owner's call-in line, or the dashboard) is logged here. Rows carry no version number; to undo a change, pick a version from list_config_versions and use rollback_config.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Max results to return (default 20, max 100).
`agent_id`	Yes	Agent ID to fetch change history for.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds that changes originate from update_agent_config, configure_agent_business_rules, the call-in line, and the dashboard. It also discloses that rows lack version numbers, which is valuable behavioral guidance, though it omits retention and ordering details.

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?

The definition is front-loaded with what is listed, then follows with source and undo context; each sentence serves a purpose. The owner call-in phrasing is somewhat colorful, but still aids understanding, with only minor verbosity.

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?

Given the rich annotations, full schema coverage, and an existing output schema, the description supplies what an agent needs to invoke this read-only audit-history tool correctly. The only minor missing operational details are ordering and retention, not core invocation requirements.

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 agent_id and limit are already documented in the input schema. The description adds no parameter-level syntax, constraints, or special semantics beyond what the schema provides, so baseline 3 is appropriate.

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?

The description uses a specific verb ('List') and resource ('agent's recent config-change audit trail'), enumerates the returned fields, and makes clear this is an audit log rather than current configuration. It names related version and rollback tools, helping distinguish it from siblings such as list_config_versions and get_agent_config.

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?

It gives clear context for consulting the change log and explicitly routes undo actions to list_config_versions plus rollback_config, preventing misuse of this read-only history tool. It does not state an explicit 'use this instead of list_config_versions when...' rule, so guidance is strong but not exhaustive.

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.