Skip to main content
Glama
rodlunt

engineering-audit

by rodlunt

get_config

Fetch the resolved audit configuration after initialization, waiting for user submission in interactive mode and raising an error on timeout.

Instructions

Fetch the resolved audit configuration.

    Requires start_config to have been called first. In preset mode the
    configuration is already known and is returned immediately. In
    interactive mode this blocks for up to timeout_s seconds waiting for
    the user to submit the configuration page; on timeout it raises a
    clear error rather than proceeding with a default configuration the
    user never actually chose. Call it again (the user's submission is
    still awaited) rather than treating a timeout as a green light.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeout_sNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations exist, so the description carries full burden. It thoroughly explains blocking up to timeout_s, the error on timeout, and that retrying still awaits the user's submission. It also clarifies that no default configuration is used, covering potential misunderstanding.

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 front-loaded with the primary purpose and each subsequent sentence adds actionable detail about modes, timeout, and retry behavior. No filler or redundant information is present.

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 tool with one parameter and an output schema, the description covers all non-obvious aspects: prerequisite, mode differences, timeout behavior, and retry semantics. It is complete enough for an agent to invoke it correctly without ambiguity.

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

Parameters5/5

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

The single parameter timeout_s is explicitly referenced and explained: it limits how long the tool waits in interactive mode. The description also clarifies what happens on timeout, which adds meaning beyond the schema's default value.

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 fetches the 'resolved audit configuration' with a specific verb and resource. It also distinguishes this from sibling tools by indicating it must follow start_config, making its role in the workflow unambiguous.

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

Usage Guidelines4/5

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

The description explicitly requires start_config to be called first and explains mode-specific behavior (preset vs interactive). It also provides a warning about timeout handling. However, it does not explicitly compare with alternative tools, so it lacks full exclusion guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rodlunt/engineering-audit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server