jury-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROQ_API_KEY | No | Optional API key for the Groq provider if configured in .jury/config.yaml. | |
| TRIAD_API_KEY | Yes | Your API key for the Constellation Gate provider, used by the default jury models. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jury_planB | Deliberate an architectural implementation plan with the multi-model jury. Synthesizes consensus readiness score, critical risks, required modifications, and an actionable file execution plan. |
| jury_reviewB | Review code changes or git diffs with the multi-model jury panel. Performs blind ballots, adversarial cross-examination, and decoupled arbitration, emitting findings, POSIX unified diff patches, and OASIS SARIF v2.1.0 diagnostics. |
| jury_askB | Consult the multi-model architecture council for targeted design advice. Returns recommended architectural pattern, confidence score, tradeoff matrix, and concrete implementation examples. |
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 3 tools
The three tools target distinct modes: implementation planning, code/diff review, and targeted design advice. jury_plan and jury_ask both involve architectural consultation, so there is some potential overlap, but their outputs and use cases are differentiated well enough.
All tools use the same jury_ prefix followed by a clear action verb: jury_plan, jury_review, jury_ask. The naming is predictable and consistent throughout.
Three tools are well-scoped for a multi-model jury server: one for planning, one for review, and one for targeted advice. Each tool has a clear purpose and earns its place.
The server covers the core consultation workflows: planning, code review, and architectural advice. Minor gaps exist around session management, follow-up deliberation, or jury configuration, but agents can work around them.