List all configured Nango environments to verify setup while keeping secret material secure. Retrieve environment details for integration and connection management.
List configured Nango environments without returning secret material.
| Name | Required | Description | Default |
|---|---|---|---|
| refresh | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.0.0Input schema / additionalPropertiesAdded value: +falsev0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully reveals that secret material is not returned, which is a safety-relevant trait, but it does not state whether the operation is read-only, how the refresh parameter behaves, or any caching or rate-limit implications.
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, tightly worded sentence with no filler. The action and resource are front-loaded, and every word adds meaning.
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 tool is simple and has an output schema, so return-value details are presumably covered elsewhere. However, the meaning of the only parameter is left undocumented and there are no annotations to cover safety or behavioral context, leaving the definition minimally viable but not complete.
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 only parameter, 'refresh', has zero schema description coverage and the tool description never mentions it. The agent cannot determine what refresh does, whether it forces a reload, or when it should be set to true, so the description fails to compensate for the missing schema documentation.
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 specifies the verb 'List' and the resource 'configured Nango environments', and adds the meaningful qualifier 'without returning secret material'. This clearly distinguishes it from sibling tools like list_integrations and list_connections.
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?
There is no guidance about when to use this tool versus alternatives such as check_environment. No exclusions, prerequisites, or alternative tool mentions are provided, so the agent must infer usage from the tool name and context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.