set_configOverride configuration keys such as gh_oc_auto and retry_delays_min to adjust automated fix and retry behavior for failing GitHub Actions workflows.
Set a configuration override (gh_oc_auto or retry_delays_min).
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | ||
| value | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description alone must disclose side effects. It only says 'override,' implying mutation but not explaining persistence, scope, or reversibility. It also doesn't mention any permissions or consequences.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, front-loaded with the action and resource, and the key enumeration is the only extra detail. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no annotations, an agent needs value-format semantics and usage context to call it correctly. The output schema covers return shape, but the description leaves the input value format and behavioral effects unspecified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description is the only source of parameter meaning. It names the two valid keys, adding real value over the generic string schema, but it does not describe the expected value format for either key (e.g., boolean vs numeric minutes).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource ('Set a configuration override') and enumerates the exact allowed keys ('gh_oc_auto or retry_delays_min'), making the tool's function unambiguous and distinct from all sibling chain-management tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no explicit when-to-use guidance or exclusions. Usage for setting those two override keys is implied by the wording, and since no sibling tool handles configuration, there are no named alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.