magicsword-mcp

Official

by magicsword-io

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

List MagicSword agent releases

list_agent_releases

Read-onlyIdempotent

Retrieve available MagicSword agent releases and per-platform latest markers to inspect before queuing an upgrade. Requires endpoints:read.

Instructions

Lists available MagicSword agent releases and per-platform latest markers before an upgrade is queued. Requires endpoints:read.

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_agent_releases"
  }
}

Input Schema

Name	Required	Description	Default
`latest`	No	Return only the latest release for the selected platform
`platform`	No	Platform used for latest filtering

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Oct 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds value beyond that by disclosing the required scope ('Requires endpoints:read') and by summarizing the payload (available releases and per-platform latest markers), though it says nothing about pagination or result size.

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?

A single sentence that front-loads what is returned and appends the prerequisite; there is no filler or restatement of the tool name.

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

Completeness4/5

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

For a two-optional-parameter, read-only listing tool with no output schema and full schema coverage, the description supplies the permission prerequisite and the shape of the result. It is nearly complete, missing only minor detail such as whether both parameters interact (latest requires platform).

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 both 'latest' and 'platform' are fully documented in the schema, including the enum values. The description adds no syntax, default, or interaction detail beyond what the schema already provides, so the 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?

States a specific verb and resource ('Lists available MagicSword agent releases') plus the scope of what is returned ('per-platform latest markers'), and the phrase 'before an upgrade is queued' implicitly separates this read-only discovery call from the mutating upgrade_endpoints sibling.

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?

The clause 'before an upgrade is queued' gives a clear workflow context in which to call this tool, which is genuine when-to-use guidance. It stops short of naming an alternative or stating exclusions, so it is not a full 5.

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