pressadvantage-mcp

list_distributions

Retrieve available distribution add-on channels for a specific release by providing its release ID. Use these channel IDs to upgrade your distribution with add_distribution_upgrade.

Instructions

List available distribution add-on channels for a release. Use the returned IDs with add_distribution_upgrade to add channels.

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": {
      "release_id": "<release_id>"
    },
    "name": "list_distributions"
  }
}

Input Schema

Name	Required	Description	Default
`release_id`	Yes	Release ID to list available distributions for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 1, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are present, so the description carries the burden. 'List' implies a read-only operation, and it adds that IDs are intended for use with add_distribution_upgrade. However, it doesn't disclose edge cases like empty results, required permissions, or whether 'available' means not yet added.

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: the first states the core purpose, the second gives actionable downstream guidance. No unnecessary words or repetition.

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 simple 1-parameter list tool without an output schema, the description provides sufficient context and the key downstream use. The term 'available' is slightly ambiguous but acceptable given the sibling tool reference.

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?

The schema has 100% coverage for the single parameter (release_id), which has a clear description. The tool description adds that these are 'distribution add-on channels' but doesn't provide deeper parameter behavior beyond what the schema already covers.

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 (list), resource (distribution add-on channels), and scope (for a release). It distinguishes from list_releases by specifying channels, and directly references add_distribution_upgrade as a related tool.

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?

Explicitly states the workflow: use returned IDs with add_distribution_upgrade to add channels. This gives clear context on when to use and pairs with a sibling tool, though it doesn't mention alternative tools or exclusions.

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