Air Pipe

update_config

Update an existing AirPipe configuration by config_uuid (config_yaml is base64-encoded YAML) and optionally redeploy.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "config_yaml": "<config_yaml>"
    },
    "name": "update_config"
  }
}

Input Schema

Name	Required	Description	Default
`role_uuid`	No
`permission`	No
`config_uuid`	No
`config_yaml`	Yes
`deploy_staging`	No
`deploy_production`	No
`organization_uuid`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 28, 2026

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided. The description mentions optional redeployment but lacks details on side effects, required permissions, idempotency, or behavior when config_uuid doesn't exist. For a mutation tool, this is insufficient.

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?

One concise sentence conveying the core purpose, key constraint (by config_uuid), encoding detail, and optional redeployment. No verbose or redundant content.

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 7 parameters, no output schema, and no annotations, the description is too sparse. The agent lacks information on how to correctly populate the request (e.g., which params are conditional, order, defaults).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description adds critical context for one parameter ('config_yaml is base64-encoded YAML'), but other parameters like 'role_uuid', 'permission', 'deploy_staging', and 'deploy_production' remain unexplained. Partial compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the verb 'update' and the resource 'AirPipe configuration', with a specific identifying field 'config_uuid' and encoding detail 'base64-encoded YAML'. It is clear but does not explicitly differentiate from sibling tool 'edit_config'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like 'edit_config' or 'deploy_config_revision'. No mention of prerequisites or scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Air Pipe tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?