Check the status of an ongoing npm install operation. Returns "idle" (no install running), "installing" (in progress), "done" (success), or "error" (failed with error message). Poll this after calling install_packages or remove_package.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | App ID (UUID) or subdomain |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description discloses the key behavioral traits: it returns the current status of an async operation and should be polled. It also explains the 'error' state includes an error message. This is sufficient for a read-only status checker, though it does not explicitly state it has no side effects.
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?
Two sentences deliver the purpose, return values, and usage timing without any redundancy or fluff. The description is well-structured and front-loaded.
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?
The description covers purpose, return value semantics, and when to use the tool. For a simple, single-parameter status checker, this is nearly complete. It could optionally detail the error message format, but that is a minor gap.
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?
The input schema fully documents the single 'app' parameter as an App ID or subdomain, covering 100% of parameters. The description adds no additional parameter detail, so the baseline score 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?
The description clearly states the tool checks npm install status and enumerates the four possible return values. It is specific to install operations, which distinguishes it from get_app_status, though it does not explicitly name alternatives.
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 explicitly instructs to poll after calling install_packages or remove_package, providing clear timing context. It does not mention exclusions or alternative tools, but the guidance is direct and useful.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes, but a few pairs could be confused: get_app vs. get_app_status both report on app state, and update_app vs. set_node_version both modify runtime configuration. Descriptions are detailed enough to mitigate most ambiguity, but the overlap is notable.
Tool names largely follow a consistent verb_noun snake_case pattern (e.g., list_apps, create_app, delete_file). Minor deviations include the bare verb 'login' and the noun-first 'git_info', which break the pattern slightly but are still understandable.
At 37 tools, the set is on the heavy side, well above the typical 3-15 range. However, the server covers a broad PaaS domain (auth, app lifecycle, file management, packages, versions, git, metrics), and each tool addresses a distinct operation. It feels over-engineered in places but not gratuitously so.
The tool surface is impressively complete for a deployment platform: authentication, app CRUD, start/stop/restart, file operations (read/write/delete/rename/search/upload), package management, version snapshots and restore, git remote and push/pull, logs, metrics, and configuration. No critical dead-ends are apparent.
