Read-only MCP adapters for LNSAT inspection contracts - policy-governed AI-agent authorization, human approval, and audit evidence
Critical failures across all dimensions. 40 tools with minimal or no visible schema definitions in source code. Tool names lack action verbs (e.g., 'lnsat.gateway.packet_inspection.v0_1' instead of 'inspect_packet'). Descriptions are generic gateway contract labels (10-50 chars), far below the 194-char baseline for production tools. No parameter descriptions visible for most tools. No documented output schemas. No error handling guidance. The codebase shows TypeScript/Rust infrastructure but tool registration details are not exposed in provided source excerpts. Per-tool analysis reveals systematic absence of LLM-optimized documentation.
Inspect audit ledger persistence readiness
Gateway contract for adapter invocation authorization bundle
Gateway contract for adapter invocation preflight
Gateway contract for adapter invocation result
Gateway contract for agent context firewall
Gateway contract for audit ledger database security preflight
Gateway contract for audit ledger migration approval preview
Gateway contract for audit ledger persistence readiness
No input schemas visible for 37 of 40 tools. Cannot verify parameter types, constraints, or descriptions.
Tool names lack action verbs. 'lnsat.gateway.packet_inspection.v0_1' should be 'inspect_packet' or 'get_packet_inspection'. Namespace-style names prevent LLMs from inferring intent from the name alone.
Descriptions are generic labels (10-50 chars), far below 194-char baseline. 'Gateway contract for packet inspection' does not explain WHAT the tool does, WHEN to use it, or what it returns. LLMs cannot select tools based on these descriptions.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 24 | 2026-07-28+ | v2 |
Gateway contract for audit ledger persistence scope request
Gateway contract for audit ledger writer interface
Gateway contract for audit ledger writer persistence preflight
Gateway contract for build packet state inspection
Gateway contract for capability broker request
Gateway contract for control center operation readback
Gateway contract for hardware allocation recommendation inspection
Gateway contract for hardware inventory inspection
Gateway contract for knowledge gateway context compilation
Gateway contract for knowledge gateway search
Gateway contract for knowledge gateway sources
Gateway contract for onboarding context inspection
Gateway contract for onboarding profile inspection
Gateway contract for packet inspection
Gateway contract for performance telemetry inspection
Gateway contract for project state inspection
Gateway contract for runtime adapter implementation approval gate
Gateway contract for runtime adapter implementation authorization request
Gateway contract for runtime adapter implementation dry run evidence
Gateway contract for runtime adapter implementation plan
Gateway contract for runtime adapter implementation scope
Gateway contract for runtime adapter readiness gate
Gateway contract for service database inventory
Gateway contract for substrate adapter manifest
Gateway contract for substrate control intent
Local control plane approval request contract
Local control plane authentication contract
Local control plane packet intake contract
Local control plane policy decision contract
Generate hash of LNSAT packet
Inspect and validate LNSAT packets
Validate LNSAT packet structure and contents
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields. Violates baseline: 100% of A+ tools have documented return types.
No error handling guidance. Tools do not indicate what to do on failure, whether errors are retryable, or how to recover. Violates pattern:recovery-guide.