list_collaboratorsList an app's collaborators (users invited to the app) and their status. Scalingo API: GET /v1/apps/{app}/collaborators. Returns { collaborators: [...] }.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already signal readOnlyHint=true. The description adds the API endpoint and return format but no further behavioral details (e.g., pagination, rate limits). It does not contradict annotations.
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 two concise sentences with no wasted words. It front-loads the key purpose and includes the API endpoint and return structure efficiently.
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 listing tool with one parameter, the description adequately covers purpose, resource, and output format. It lacks mention of potential limitations like pagination, but this is not critical for the tool's simplicity.
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 coverage is 100% and the description repeats the parameter's name and gives an example value, but adds minimal meaning beyond the schema. Baseline 3 is appropriate.
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 action (list), resource (an app's collaborators), and additional detail (status). It also mentions the API endpoint and return format, making it unambiguous and distinct from sibling tools.
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 is provided on when to use this tool versus alternatives like list_apps or list_domains. There is no mention of prerequisites or scenarios where this tool is appropriate.
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.
Each tool targets a distinct resource or action: get_app vs get_app_logs vs get_app_stats are clearly different; list_addon_providers vs list_addons differentiate available vs provisioned. Mutation tools (restart, scale, trigger_deployment, set_variables) are unique. The fallback scalingo_request is a separate generic GET. No confusion between tools.
All tools use snake_case with a verb_noun pattern (get_, list_, restart_, scale_, trigger_, set_). The only exception is 'scalingo_request' which breaks the pattern, but it is clearly documented as a power-user escape hatch. Overall very consistent.
21 tools is well-scoped for a PaaS platform covering core resources like apps, deployments, addons, domains, env variables, and collaborators. It covers the essential operations without being bloated; each tool serves a clear purpose.
The toolset is heavily read-oriented; mutations are limited to restart, scale, set_variables, and trigger_deployment. Missing CRUD for major resources: no create/delete app, add/remove collaborators, add/remove domains, provision/delete addons, or update app settings. Agents will face dead ends when needing to perform writes beyond the few covered.