list_organizations
List the organizations you belong to and their organization_uuid. Call this first to get an organization_uuid for the config tools.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Air Pipe
by io.airpipe
TDQS
A4.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the basic behavior (listing) but lacks details on safety, side effects, or response structure. It is minimally adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that efficiently conveys both purpose and usage order without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, simple list tool, the description fully covers what the agent needs: the action, the output hint, and the integration context with sibling tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters. The description adds value by explaining the output field (organization_uuid) that can be used later, which is helpful beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists organizations and their organization_uuid. It distinguishes from sibling config/module tools by explicitly identifying this as a prerequisite.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly instructs to call this first to obtain organization_uuid for config tools, providing clear when-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.3/5.0
Disambiguation5/5
Each tool targets a distinct resource (config or module) and action (create, read, update, delete, deploy, etc.), with clear descriptions that avoid overlap. No two tools appear to perform the same function.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_config, list_modules), with occasional specificity like deploy_config_revision. No mixing of conventions or unexpected naming.
Tool Count4/5
At 19 tools, the count is slightly above the typical 3-15 range but still well-scoped for a configuration management server covering CRUD, deployment, revision history, validation, and planning. Each tool earns its place.
Completeness4/5
The tool surface covers the full lifecycle of configurations and modules (create, read, update, delete, deploy, undeploy, toggle, validate, plan, edit). Minor gaps like bulk operations or search are absent but not critical for the domain.