tteop-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tteop_build_envelopeA | Build a TTEOP v0.1-draft schema-conforming telemetry envelope from token counts. Computes Yield (Υ), Leverage (L), Velocity (V), output_fraction (F), and log_leverage (D). No data is submitted or persisted. Returns the complete envelope as JSON. |
| tteop_validate_envelopeA | Validate a TTEOP v0.1-draft telemetry envelope against the JSON Schema and semantic rules. Returns validation status, schema errors, semantic errors, warnings, and computed metrics if valid. |
| tteop_describe_protocolA | Get TTEOP protocol metadata: version, supported versions, privacy modes, provenance levels, forbidden fields, metric definitions (formulas, symbols, rounding), and schema/spec URLs. |
| tteop_run_conformanceA | Run the TTEOP conformance suite: canonical vector invariants, zero-input/zero-output null semantics, missing-cache handling, build-validate round-trip, forbidden field detection, and banker's rounding. Returns pass/fail counts and detailed results. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct operation: building an envelope, validating a single envelope, describing protocol metadata, and running the conformance suite. Even though validate and conformance both involve validation, their scope is clearly separated and descriptions make the distinction obvious.
All tool names share the tteop_ prefix and follow a consistent snake_case verb_noun pattern: validate_envelope, describe_protocol, run_conformance, build_envelope. This makes the tool set highly predictable.
Four tools is well-scoped for a focused protocol-support server. Each tool serves a clear core workflow—build, validate, describe, and test—without unnecessary bloat or missing essentials.
The set covers the primary lifecycle for TTEOP envelopes: construction, validation, protocol introspection, and conformance testing. A minor gap is the lack of a dedicated parse/decode tool, but build and validate together cover the main practical workflows.