get_config
Get a single configuration's data by config_uuid, optionally with its revisions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| config_uuid | 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
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so description must carry the burden of behavioral disclosure. It states 'Get' implying read-only, but fails to mention authentication requirements, response format, or the fact that the 'revisions' option is not reflected in the schema. This omission reduces transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence is concise, but the phrase 'optionally with its revisions' is ambiguous given the schema, making it less effective. Could be more precise without increasing length.
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?
For a tool with no output schema and no annotations, the description should explain what 'data' includes and how revisions are handled. It lacks details on return values, pagination, or error conditions, 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?
With 0% schema description coverage, the description needs to compensate. It adds meaning by identifying config_uuid as the lookup key and hinting at revisions, but the revisions hint is unsupported by the schema, causing a mismatch. Does not clarify the organization_uuid parameter.
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?
Description clearly states verb 'Get', resource 'configuration data', identifier method 'by config_uuid', and optional feature 'with revisions'. It effectively distinguishes from siblings like list_configs and create_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?
The description mentions an optional 'revisions' feature but the input schema has no corresponding parameter, causing confusion. No guidance on when to use this tool versus siblings like get_module or plan_config, and no prerequisites or limitations.
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.