edit_config
Edit an AirPipe configuration YAML with a natural-language instruction.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| instruction | Yes | ||
| current_yaml | Yes | ||
| organization_uuid | Yes |
Air Pipe
by io.airpipe
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose behavioral traits such as side effects, permissions, or validation behavior. The term 'Edit' implies mutation but lacks detail.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that front-loads purpose. It is concise with no wasted words, though it could include more helpful detail while remaining brief.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations, no output schema, and 18 sibling tools, the description is too sparse. It fails to explain return values, prerequisites, or how it differs from update_config or plan_config, leaving the agent underinformed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%. The description only vaguely references the 'instruction' parameter via 'natural-language instruction', but does not explain organization_uuid or current_yaml. It adds minimal meaning 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 action ('Edit'), the resource ('AirPipe configuration YAML'), and the method ('natural-language instruction'). This distinguishes it from sibling tools like create_config or validate_config.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage (editing via natural language) but provides no explicit guidance on when to use this tool versus alternatives like update_config or plan_config. No exclusions or prerequisites are mentioned.
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.