Retrieve detailed information for a specific app using its UUID, enabling inspection of configuration and status for deployment and diagnostic tasks.
Get detailed information about a specific app.
| Name | Required | Description | Default |
|---|---|---|---|
| app_id | Yes | App ID (UUID) |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds nothing beyond that – it does not say what "detailed information" comprises or how an unknown/invalid app_id is handled.
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 waste. It is appropriately sized for a trivial getter, though the word "detailed" carries little 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 getter with rich annotations and full schema coverage, minimal description is defensible. Still, there is no output schema and no hint about what fields are returned or what happens when the app does not exist.
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 single parameter is documented as "App ID (UUID)" in the schema. The description adds no meaning beyond that, so the baseline of 3 applies.
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 ("Get detailed information") and resource ("a specific app"), which is clearly distinguishable from mutating siblings like update_app or delete_app. It does not explicitly contrast with list_apps, but "a specific app" plus the required app_id makes the distinction reasonably clear.
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 explicit guidance on when to use this versus deployado_list_apps (to discover IDs) or deployado_get_deployment (for deployment-level detail). Usage is only inferable from the required app_id parameter.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.