Skip to main content
Glama

governance-platform

by ai.geodesiclabs
OverviewDiscussionsAdmin

repair

Read-onlyIdempotent

One-shot repair: return corrected values that would make failing data valid under the Blueprint. Use repair_path to see the steps instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYesGeodesicAI API key (gai_...)
blueprintNoBlueprint name (workflow_name) to use
structured_dataYesThe document's extracted fields as key/value pairs. Keys are open by design - your Blueprint's rules define what is checked
derivation_rulesNoMath rules as objects. Types: add, subtract, multiply, divide, round, copy, sum (multi-operand), items_multiply, items_sum. Each needs 'type' plus its fields; see the blueprint_guide prompt
formal_constraintsNoConstraint objects. Types incl. magnitude_anchor {field,min,max}, relative_anchor {field,reference_field,ratio_min,ratio_max}, max_action_threshold {field,threshold,on_violation}, required_fields {fields}, equals, range, in_set, regex_match, items_magnitude_anchor; see the blueprint_guide prompt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / api_key / description
      Added value: +"GeodesicAI API key (gai_...)"
    • addedInput schema / properties / blueprint / description
      Added value: +"Blueprint name (workflow_name) to use"
    • addedInput schema / properties / derivation_rules / description
      Added value: +"Math rules as objects. Types: add, subtract, multiply, divide, round, copy, sum (multi-operand), items_multiply, items_sum. Each needs 'type' plus its fields; see the blueprint_guide prompt"
    • addedInput schema / properties / formal_constraints / description
      Added value: +"Constraint objects. Types incl. magnitude_anchor {field,min,max}, relative_anchor {field,reference_field,ratio_min,ratio_max}, max_action_threshold {field,threshold,on_violation}, required_fields {fields}, equals, range, in_set, regex_match, items_magnitude_anchor; see the blueprint_guide prompt"
    • addedInput schema / properties / structured_data / description
      Added value: +"The document's extracted fields as key/value pairs. Keys are open by design - your Blueprint's rules define what is checked"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare the tool read-only, idempotent, and non-destructive. The description adds that it returns corrected values and is one-shot, which clarifies the output behavior and invocation model beyond what annotations state. This is more than the minimal bar, so a 4 is warranted.

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 extremely concise: two sentences that front-load the core action ('One-shot repair') and immediately provide a key alternative. No wasted words; every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no output schema but the description explains the return value (corrected values), and the schema fully documents all parameters, the description is complete enough for an agent to select and invoke it correctly. It does not cover edge cases like already-valid data, but that is not essential for basic invocation.

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

Parameters3/5

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

The input schema covers all five parameters with 100% description coverage, so the schema already provides the necessary parameter semantics. The description does not add parameter information, but it does not need to; the baseline of 3 is appropriate.

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 identifies the tool as a one-shot repair that returns corrected values for failing data under the Blueprint. It uses a specific verb and resource, and explicitly distinguishes itself from the sibling tool repair_path by contrasting the one-shot output with step-by-step guidance.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool versus repair_path: use repair for the corrected values directly, and use repair_path to see the steps. This satisfies the when-to-use and when-not-to-use criteria, even though it does not mention all other siblings.

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

All governance-platform toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources