Skip to main content
Glama
PsYcGoD

SAGE

by PsYcGoD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sage_agentic_fix

Return the single best fix candidate for a failed SAGE command. Use when you need one actionable repair plan, not a list of alternatives. Input is an optional SAGE run id; when omitted, the most recent failed run is analyzed.

Instructions

Return the single best fix candidate for a failed SAGE command. Use when you need one actionable repair plan, not a list of alternatives. Input is an optional SAGE run id; when omitted, the most recent failed run is analyzed. Returns fix_command, strategy, confidence, and explanation, or null when no safe fix is known. Read-only: does not execute the fix and does not edit files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
command_idNoOptional SAGE run id of the failed command. Omit to use the most recent failed command.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.6.2
  2. Removedv2.5.1
  3. Changed2 schema fields changedv2.4.22
    • changedInput schema / properties / command_id / description
      Previous value: -"Specific command ID (optional, defaults to last failed)"New value: +"Optional SAGE run id of the failed command. Omit to use the most recent failed command."
    • addedInput schema / properties / command_id / minimum
      Added value: +1
  4. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Discloses read-only behavior: 'does not execute the fix and does not edit files'. Also mentions return null when no safe fix is known. No annotations provided, but description fully covers behavioral traits.

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?

Three sentences, front-loaded with purpose, no wasted words. Efficient and clear.

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?

Given one optional param, no output schema, description covers purpose, usage, behavior, parameter semantics, and return values. Complete and self-contained.

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?

Schema has 100% coverage for the single parameter. Description adds meaning: explains optionality and default behavior ('when omitted, the most recent failed run is analyzed').

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 'Return' and resource 'single best fix candidate for a failed SAGE command'. Distinguishes from alternatives by specifying 'not a list of alternatives'.

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?

Explicitly says 'Use when you need one actionable repair plan, not a list of alternatives', providing clear usage context. Could be improved by explicitly naming the alternative sibling tool (e.g., sage_suggest_fix).

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

Deploy Server

Other Tools