Skip to main content
Glama

TraceCheck

Server Details

Scores an AI agent's execution trace 0-100 and returns concrete fixes. Free, no API key.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
TGS-checker/tracecheck-mcp
GitHub Stars
0
Server Listing
Tracecheck
ChatGPT
–
Claude
–

TDQS

A4.6/5.0

Scored across 2 tools

Disambiguation5/5

The two tools serve clearly separate purposes: evaluate_trace performs the scoring, while get_trace_schema only returns format documentation and is explicitly 'call once before your first evaluate_trace'. Descriptions even cross-reference each other, so an agent cannot mistake which to call for which need.

Naming Consistency5/5

Both names use a strict snake_case verb_noun pattern (evaluate_trace, get_trace_schema) with the shared resource token 'trace'. No camelCase or stylistic drift.

Tool Count3/5

Two tools is at the thin end of the scale, and one is purely a documentation helper, leaving a single functional operation. That is defensible for a narrow, single-purpose checker, but the surface feels minimal rather than well-rounded.

Completeness4/5

The evaluation lifecycle is essentially covered: learn the format via get_trace_schema, then submit goal/trace/outcome for a scored report with issues and suggestions. Minor gaps exist around history/comparison between runs and batch traces, which the 'THE LOOP' guidance implies but no tool supports.

Available Tools

2 tools
evaluate_traceAInspect

Get an independent, deterministic reliability check of a multi-step task you (an agent) just ran. Returns a 0-100 score, the issues found, and concrete fixes to apply on your next attempt.

WHEN TO CALL: after you finish (or give up on) a multi-step task that used tools, before you report "done" to the user, or after a failure you want to learn from. Free, no API key, fast and offline (keyword heuristics, no LLM). Call get_trace_schema first if unsure of the format.

INPUT (all plain strings):

  • goal: the original task, stated specifically (what success looks like). Vague goals under 20 chars are penalised.

  • trace: your chronological steps, one per line, e.g. "1. Called search_flights(AMS->LIS) -> returned 3 results" / "2. Observed: ..." . Write what each tool RETURNED ("observed", "returned", "result:"), any error and the retry/fallback you used, and a final "Verified: ..." line.

  • outcome: the concrete final result you claim, and how it meets the goal.

  • agent_name: optional identifier for yourself (logging only).

RETURNS JSON: score (int 0-100), dimensions {goal_clarity, observability, error_recovery, goal_alignment, efficiency}, issues (list), suggestions (list, max 5), summary, version.

THE LOOP: run task -> evaluate_trace -> apply the suggestions to your process -> re-run -> evaluate_trace again and compare scores/dimensions. Scores below ~60 usually mean missing observations, unrecovered errors, repeated steps (loops), success claimed without evidence, or no verification step.

Inputs: goal (required), trace (required), outcome (required), agent_name.

get_trace_schemaAInspect

Return the exact input format TraceCheck's evaluate_trace expects, the scored dimensions and weights, and a complete example call you can copy. Call this once before your first evaluate_trace. No arguments, no side effects.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.