agentflight
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| agentflight_diff_cassettesA | Compare a baseline golden AgentFlight cassette against a candidate cassette to detect behavioral regressions. PurposePerforms semantic trajectory diffing across model, prompt, or tool definition upgrades. Evaluates tool sequence divergence using Levenshtein distance and Longest Common Subsequence (LCS), identifies newly introduced tool failures, flags recursive loop regressions, and calculates token spend and USD cost deltas. When to use
When NOT to use
Behavior & Side Effects
|
| agentflight_export_otelA | Export recorded AgentFlight cassette spans into W3C TraceContext and OpenTelemetry JSON traces. PurposeConverts recorded agent execution spans into OpenTelemetry-compliant trace spans with standard gen_ai semantic conventions, enabling critical-path latency waterfall visualization and distributed tracing in systems like StackPulse, Jaeger, or Datadog. When to use
When NOT to use
Behavior & Side Effects
|
| agentflight_lint_toolsA | Statically inspect MCP tool schema definitions against 10 ergonomics rules (TS001-TS010) and calculate an Agent Ergonomics Score. PurposeEvaluates Model Context Protocol tool schemas for anti-patterns that confuse LLM tool-calling (tautological descriptions, missing required arrays, ambiguous parameter types, unconstrained inputs, and lack of usage boundaries). Produces an ergonomics score (0-100) and actionable remediation steps. When to use
When NOT to use
Behavior & Side Effects
|
| agentflight_verify_cassetteA | Cryptographically verify the SHA-256 hash chain and structural integrity of an AgentFlight cassette. PurposeValidates that a recorded agent execution cassette (.flight.json or .flight.jsonl) has not been tampered with, truncated, or corrupted. Verifies that every span links to the previous span digest via canonical JSON SHA-256 hashing. When to use
When NOT to use
Behavior & Side Effects
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| lint-tool-definitions | Review and harden MCP tool definitions against the 10 AgentFlight tool-smell rules (TS001-TS010) to maximize LLM tool-calling accuracy. |
| review-agent-trajectory | Architectural post-mortem prompt to analyze an AI agent trajectory for repetitive loops, runaway token spend, or tool errors. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| MCP Tool-Smell Linter Rule Catalog (TS001-TS010) | Comprehensive specification of the 10 static ergonomics rules for MCP tool definitions, including severity, antipattern signatures, and suggested fixes. |
| AgentFlight Performance Benchmarks & Subsystem Specs | Deterministic trajectory replay latency (<0.02ms), tool-smell linter throughput (1,676 tools/sec), and zero-overhead circuit-breaker benchmarks. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct action and output: verify (crypto integrity), diff (behavioral regression), export (OTel traces), and lint (schema ergonomics). Descriptions even include explicit "When NOT to use" cross-references pointing to the correct sibling tool, eliminating overlap. An agent can select unambiguously from names alone.
All four tools follow an identical `agentflight_verb_noun` snake_case pattern: diff_cassettes, export_otel, lint_tools, verify_cassette. The shared server prefix plus a clear action verb keeps the set predictable and readable.
Four tools is a tight, well-scoped surface for a cassette verification/observability toolkit, and each tool maps to a distinct lifecycle stage rather than duplicating functionality. Nothing appears padded or redundant.
The analysis/verification side of the domain is well covered (verify, diff, export, lint), but there is no tool to record, list, or replay cassettes — replay is delegated to an external `agentflight.replayer` CLI. This is a workable but noticeable gap for an agent trying to run a full record-verify-diff-replay loop from MCP alone.