Loading ToolBench
AXL Protocol v3: Compressed semantic protocol for agent reasoning. Deterministic English-to-AXL compression.
This is a Python library, not an MCP server. No MCP transport layer detected (STDIO, HTTP, or SSE). Tools are Python functions with minimal schema documentation. 19 tools have basic descriptions (10-100 chars, below the 194-char baseline), but input schemas are inferred from docstrings, not formally registered. Parameters lack type constraints, enums, and detailed descriptions. No error handling guidance, no output schema documentation, and no security considerations. The codebase is a domain-specific compression library for the AXL protocol, not an agent-facing MCP server.
Compress English text to AXL v3 packets using entity aliasing and semantic compression
Decompress AXL v3 packets to readable English prose
Decompress AXL v3 packets to English claims with operation and confidence
Detect whether a packet is v1 or v3 format
Emit a Packet as an AXL pipe-delimited string
Emit a V3Packet as a pipe-delimited AXL v3 string
Convert English text to AXL v3 packet format
Not an MCP server, this is a Python library with no MCP transport layer (STDIO, HTTP, or SSE). Cannot be used as an MCP server without wrapping in an MCP server implementation.
Input schemas are inferred from docstrings, not formally defined. No JSON Schema with type constraints, enums, or parameter descriptions visible in code. All 19 tools lack explicit schema registration.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 34 | 2026-07-28+ | v2 |
Format decompressed AXL output for display
Parse a raw AXL packet string into a Packet dataclass
Parse a single AXL v3 packet line into a dictionary
Parse a v3 AXL packet string into a V3Packet
Strip kernel/manifest metadata from AXL output
Translate a v1 Packet to English prose
Convert a v1 Packet to JSON format
Build a V3Packet from an application/vnd.axl+json dict
Translate a V3Packet to English prose
Convert a V3Packet to application/vnd.axl+json format
Validate an AXL v1 packet and return ValidationResult with errors and warnings
Validate a v3 AXL packet and return list of error strings
Tool descriptions are too brief (10-100 chars vs 194-char baseline). Descriptions lack context on WHEN to use each tool, WHAT it returns, and dependencies between tools (e.g., parse must precede validate).
No output schema documentation. Tools return dataclass instances (Packet, V3Packet, ValidationResult) but LLMs cannot see the structure of returned fields. No guidance on what fields to expect or how to chain results to downstream tools.
No error handling guidance. Tools may raise exceptions (e.g., parse() on malformed input) but descriptions do not explain failure modes, recovery steps, or what the LLM should do next.