Skip to content
Eden Engine

AI Agent Trace Failure Analysis

omnial/x402-agent-trace-analyze

Given a pasted agent execution trace/log (LangChain, CrewAI, or AutoGen), returns the point and type of failure, a root-cause explanation, a suggested fix, a step-by-step summary of the run, any failure patterns detected (e.g. retry loops), and a token-usage breakdown. A trace with no failures returns a clean-run report instead.

activeper callv1
Provider
Web & Business Data Network
Category
developer-tools
Provider price
$0.324324 per call
Latency p50 / p95
— / —
Success rate
—
Verified
—

Provider list price; Omnial MCP charges provider cost plus a platform markup on top.

Contract

input_schema.json
{
  "type": "object",
  "required": [
    "trace"
  ],
  "properties": {
    "trace": {
      "type": "string",
      "description": "Agent log/trace output"
    }
  },
  "additionalProperties": false
}
output_schema.json
{
  "type": "object",
  "properties": {
    "_meta": {
      "type": "object",
      "properties": {
        "provenance": {
          "type": "object",
          "properties": {
            "fetched_at": {
              "type": "string",
              "description": "ISO 8601 timestamp of when the analysis was generated."
            }
          },
          "additionalProperties": true
        }
      },
      "description": "Analysis metadata. Only the timestamp below is kept; internal capability/latency/payment/model-provenance fields observed at this same level are not surfaced (see this tool's verification.notes).",
      "additionalProperties": true
    },
    "severity": {
      "type": "string",
      "description": "Observed as \"warning\" (a failing run that still produced a final answer) and \"info\" (a clean run) across the two real fixtures -- other levels (e.g. a hard \"error\"/\"critical\") are plausible but unconfirmed."
    },
    "root_cause": {
      "type": "string",
      "description": "Prose explanation of why the failure happened, or \"No failures detected in execution trace\" on a clean run."
    },
    "step_count": {
      "type": "number",
      "description": "Number of entries in steps_summary."
    },
    "failure_type": {
      "type": "string",
      "description": "A short failure category, e.g. \"tool_error\". The literal string \"none\" on a clean run."
    },
    "trace_length": {
      "type": "number",
      "description": "Character length of the trace text that was analyzed."
    },
    "failure_point": {
      "type": "string",
      "description": "Where in the trace the failure occurred, in prose. The literal string \"none\" on a clean run (crewai-clean-run.json)."
    },
    "steps_summary": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "step": {
            "type": "number",
            "description": "1-indexed step number."
          },
          "action": {
            "type": "string",
            "description": "What happened at this step, in prose."
          },
          "status": {
            "type": "string",
            "description": "Observed values: \"success\", \"failure\", \"warning\" across the two real fixtures."
          }
        },
        "additionalProperties": true
      },
      "description": "One entry per step the analyzer identified in the trace, in order."
    },
    "suggested_fix": {
      "type": "string",
      "description": "Prose suggestion for fixing the failure, or \"N/A - execution completed successfully\" on a clean run."
    },
    "patterns_detected": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Named failure patterns the analyzer recognized (e.g. \"loop_detected\", \"excessive_retries\", \"no_backoff_strategy\"). Empty on a clean run."
    },
    "token_usage_breakdown": {
      "type": "object",
      "properties": {
        "total": {
          "type": "number"
        },
        "estimated_input_tokens": {
          "type": "number"
        },
        "estimated_output_tokens": {
          "type": "number"
        }
      },
      "description": "Estimated token usage for the analyzed run.",
      "additionalProperties": true
    }
  },
  "description": "The trace-analysis result, as returned at routing.responseResultPath.",
  "additionalProperties": true
}

Pricing

Every real charge, itemised. A model that quietly omits one is a slow financial leak, so nothing here is rolled up, and a charge that only applies to some inputs says so rather than being added in.

Prices in this catalog are the provider's own list price, not your bill: Omnial MCP charges provider cost plus a platform markup on top, so what you are charged is higher than the figure shown. For the exact amount a specific call will cost, run omnial_execute with dry_run: true; that number includes the markup and is what we hold while the call runs. It is a quote, not a cap on the charge.

ChargeRate
Per call
Flat, regardless of what comes back
$0.324324
Cost basis
Not recorded

This tool's catalog entry does not record how its final bill is determined, so we will not tell you whether its cost is fixed before the call or reported by the provider afterwards. Either way what is held is a quote rather than a cap: you are charged what the call actually costs, bounded at 2x the quote.

Updated
Sep 23, 2026