amp-mcp-server

Get application update info

amp_get_update_info

Check if a game-server update is available for an AMP instance, retrieving the available version, build number, and release notes URL.

Instructions

Check whether a game-server update is available for one AMP instance. Returns the available version, build, and release notes URL.

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": {
      "instanceId": "<instanceId>"
    },
    "name": "amp_get_update_info"
  }
}

Input Schema

Name	Required	Description	Default
`instanceId`	Yes	Instance UUID, as returned by amp_list_instances

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1May 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It implies read-only behavior ('check') but does not explicitly state it has no side effects or mention authentication needs. The return fields are listed, which is helpful.

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?

Single sentence, front-loaded with the purpose, no redundant words. Information is efficiently packed.

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?

For a simple 1-parameter tool with no output schema, the description adequately covers purpose, input, and return values. No gaps identified.

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?

Input schema covers the sole parameter with a clear description. The tool description does not add significant new semantics beyond what the schema already provides, so baseline 3 applies.

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 ('Check whether...available') and resource ('game-server update for one AMP instance'). It also lists specific return fields, distinguishing it from siblings like amp_get_instance_status.

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 for a single instance but does not provide explicit guidance on when to use this tool over siblings or mention any prerequisites beyond the instanceId.

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

Deploy Server