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
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.4/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries the burden. It indicates a read operation ('Get'), but lacks details on behavioral traits like whether revisions are returned by default, authentication needs, or side effects. The description is too brief.
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, concise sentence that communicates the core purpose and key optional behavior. Every word earns its place with no fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (get by ID), no output schema, and minimal annotations, the description is adequate but not thorough. It covers the basic purpose but misses details on return format, error scenarios, and revision behavior.
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%, so the description must compensate. It mentions 'by config_uuid' but does not describe the 'organization_uuid' parameter or add any format or meaning beyond the schema. The optional 'with its revisions' is a behavioral note, not parameter-level detail.
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 'Get a single configuration's data' using a specific verb and resource, and distinguishes from sibling tools like create_config, delete_config, and list_configs. The optional 'with its revisions' adds specificity.
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?
No explicit guidance on when to use this tool versus alternatives. The description implies it's for retrieving a specific configuration, but does not mention when to prefer it over list_configs or other get operations.
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.4/5.0
Disambiguation5/5
Every tool has a clearly distinct purpose, targeting either configs or modules with specific actions (create, get, list, delete, update, deploy, etc.). The only potential overlap is between edit_config and plan_config, but they serve different stages of config management (editing vs. authoring).
Naming Consistency4/5
The naming follows a verb_noun pattern consistently (e.g., create_config, delete_config, list_configs). Minor inconsistency: 'list_configs' uses plural while most others use singular (config). Overall, the pattern is predictable and clear.
Tool Count4/5
With 19 tools, the count is slightly above average but justified by the need to manage two resource types (configs and modules) with full lifecycle operations including deployment, revision handling, and validation. It is well-scoped for a configuration management server.
Completeness5/5
The tool surface is comprehensive, covering CRUD for both configs and modules, plus deployment, undeployment, toggling, revision management, editing via NL, planning, and validation. No obvious gaps for the intended domain.