Skip to main content
Glama
Sign In
apollo-mcp-server

apollo-mcp-server

by iceycn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

rollback_release

Roll back a configuration release to a specified version using the release ID from the latest release.

Instructions

回滚到指定版本。releaseId 为发布记录 ID，从 get_latest_release 返回的 id 字段获取。

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": {
      "env": "<env>",
      "releaseId": "<releaseId>",
      "operator": "<operator>"
    },
    "name": "rollback_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
envYes
releaseIdYes发布记录 ID，从 get_latest_release 返回的 id 字段获取
operatorYes操作者，域账号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only says 'rollback' which implies a state change, but lacks disclosure of destructive effects, prerequisites, or any behavioral traits beyond the name.

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?

Two concise sentences, no wasted words. Front-loaded with the primary action. Efficient for a simple tool.

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 three required parameters and no output schema or annotations, the description is incomplete. It does not explain return values, error conditions, or prerequisites like the need for a previous release. A rollback is a significant action, and the lack of context leaves the agent underinformed.

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 67% (2/3 params described). The description adds minimal extra context for releaseId (where to get it), but adds no meaning for env or operator. Baseline 3 since coverage is high but description does not fully compensate for missing param descriptions.

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 action 'rollback' and the resource 'release', with a specific verb and resource. It also references a sibling tool (get_latest_release) for obtaining the required releaseId, distinguishing itself from publish_release.

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

Usage Guidelines3/5

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

The description implies usage by explaining where to get the releaseId (from get_latest_release), but does not provide explicit guidance on when to use rollback vs alternatives like publish_release, nor when not to use it.

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