LiDAR Harness 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| harness_initA | Initialize LiDAR Harness for a project: detect typecheck/lint commands, establish baselines, classify task complexity. Call this ONCE at the start of a session. Provide the user's task message for complexity classification. Returns: session info with detected commands, complexity, and PGO readiness. |
| harness_classifyA | Classify a task as "simple" (question, explanation) or "complex" (implementation, refactor, fix). Simple tasks skip PGO and review overhead entirely. Call before starting work. |
| harness_pgoA | Run incremental PGO (Pose Graph Optimization) typecheck/lint verification. KEY CONCEPT: Only returns NEW errors not seen in previous calls. If you call it 10 times, each call only shows errors that appeared SINCE the last call. When it returns 0 new errors, the code compiles cleanly. Use after each agent turn that modifies code to verify incrementally. |
| harness_reviewA | Run multi-perspective code review: security scan (secrets in git diff), correctness (uncommitted changes), style (lint results). Call periodically (e.g. every 3rd turn) to catch issues the agent might miss. |
| harness_resetA | Reset PGO baselines and shown-errors state for a fresh start. Call when switching to a new task or after significant dependency changes. |
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 5 tools
Tools have distinct purposes but some overlap exists: harness_classify and harness_init both classify task complexity, which could cause confusion about which to use. The descriptions help clarify, but ambiguity remains.
All tools follow a consistent 'harness_' prefix with descriptive, uniform naming (classify, init, pgo, reset, review), all in lowercase with underscores.
5 tools is well-scoped for a harness tool. Each covers a distinct phase: pre-work classification, initialization, incremental verification, reset, and periodic review.
The tool surface covers the core workflow but is missing a status/list tool to show current baselines or state, which could be useful. Still, major operations are covered.