Retrieve all Fly.io apps in your organization using an API key and optional org slug. Use this to inventory deployed apps before automation or management tasks.
List all Fly.io apps in your organization.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Fly.io API token | |
| org_slug | No | Organization slug (optional) |
Changes observed during successful MCP inspections.
v0.1.9v0.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds only the organizational scoping context, and omits pagination behavior, result size, and what happens when org_slug is absent.
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?
A single front-loaded sentence with zero filler. Nothing redundant or trailing.
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 simple read-only list tool with rich annotations and full schema coverage, the definition is minimally adequate. It leaves unclear whether the list is paginated, whether api_key must be supplied despite being marked optional, and how the optional org_slug changes the result set.
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%, so both api_key and org_slug are documented in the schema and the baseline of 3 applies. The description reinforces that results are org-scoped but adds no syntax or format detail beyond what the schema already says.
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?
States a specific verb and resource: list Fly.io apps. Scope is qualified as 'in your organization.' However, it does not differentiate from siblings like fly_get_app, fly_list_machines, or fly_list_volumes, so an agent must infer the boundary itself.
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?
No guidance on when to use this versus fly_get_app for a single app or other Fly.io list tools. No prerequisites or exclusions are stated; usage is entirely implied by the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.