Skip to main content
Glama
Sign In
MegaCloud MCP Server

MegaCloud MCP Server

Official
by megaease
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_middleware_instance_change_events

View a chronological list of change events for a specified middleware instance to audit modifications and track updates.

Instructions

List all change events of a middleware instance.

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": {
      "middleware_instance_name": "<middleware_instance_name>"
    },
    "name": "list_middleware_instance_change_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
middleware_instance_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states 'list', implying a read operation. No behavioral details such as ordering, pagination, or what constitutes a 'change event' are disclosed.

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, very concise. However, it lacks important contextual information, so while compact, it could be expanded slightly for clarity without losing efficiency.

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

Completeness2/5

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

Given the tool's simplicity (1 parameter, no output schema), the description should at least explain what change events are or how to use the parameter. It falls short, leaving the agent with insufficient context.

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 description coverage is 0%, so the description must add meaning. While the parameter name is self-explanatory, the description does not elaborate on its usage or format, providing no added value beyond the schema.

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?

The description clearly states the tool lists change events of a middleware instance, using a specific verb and resource. However, it does not distinguish from sibling tools like list_middleware_instance_logs or list_middleware_instance_monitor_data, missing differentiation.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or scenarios where this tool is appropriate.

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

Deploy Server

Other Tools