Lists recent deployments in newest-first order and optionally filters results to a single host, helping you review deployment history and find recent changes.
Recent deployments (newest first), optionally one host.
| Name | Required | Description | Default |
|---|---|---|---|
| host_id | No | Restrict to one host |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds useful behavioral context by stating results are newest first, but it does not define how many 'recent' deployments are returned or whether pagination applies.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single compact sentence that front-loads the resource and ordering with no wasted wording. Every phrase contributes useful information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter, read-only list tool with a full schema, rich annotations, and an output schema, the description is largely sufficient for correct invocation. The main remaining ambiguity is the scope of 'recent' and any result limit, but that is not required to call the tool successfully.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the host_id parameter is already documented as 'Restrict to one host.' The description's 'optionally one host' duplicates that schema information without adding format or edge-case semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies the resource (deployments), the ordering (newest first), and the optional host filter. It is clear what the tool returns, but it does not explicitly name a verb such as 'list' or distinguish itself from sibling actions like deploy_push and deploy_verify.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives such as deploy_verify, deploy_push, or the other *_list tools. The only conditional detail, 'optionally one host,' describes filtering rather than tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.