iSuite Operations MCP Server

list_recent_changes

Retrieve system-level changes such as configuration updates, role changes, or schedule modifications within a specified time window. Filter by change type and limit results.

Instructions

List recent system-level changes (config updates, role changes, schedule modifications) within a time window.

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

Input Schema

Name	Required	Description
`hours`	No	Look-back window in hours (default 24).
`changeTypes`	No	Filter by change types: 'config', 'role', 'schedule', 'user', 'batch'.
`limit`	No	Maximum results to return (default 50).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 13, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action and resource, but does not mention permissions, rate limits, data freshness, or side effects. This is insufficient for an agent to understand the tool's behavior.

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 description is a single sentence that efficiently conveys the core function. It is concise and front-loaded with the key action, though it could be restructured to highlight important details like filtering capabilities earlier.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (3 parameters, no output schema), the description provides sufficient context for what it lists but lacks details about return format, ordering, or pagination. It is adequate but not fully complete.

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 description coverage is 100%, so the baseline is 3. The description adds no extra meaning beyond the schema's parameter descriptions; it only reiterates the time window concept. Thus, it meets but does not exceed the baseline.

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 clearly states the verb 'list' and the resource 'recent system-level changes', with specific examples (config updates, role changes, schedule modifications). It distinguishes from sibling tools by focusing on system-level changes over a time window, which is unique among the listed siblings.

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

Usage Guidelines2/5

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

The description does not provide any guidance on when to use this tool versus alternatives. It mentions a time window but lacks explicit when-to-use, when-not-to-use, or comparison to siblings like get_audit_log or list_user_activity.

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