Schema | clef-mcp

clef-mcp

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`CLEF_HOME`	No	Cache/model home	~/.cache/clef-mcp
`CLEF_MODEL`	No	Model id (`clef_decide` also accepts a per-call `model`)	clef-flash
`CLEF_RUNTIME`	No	Inference runtime (v0.1: only llama-cpp)	llama-cpp
`CLEF_LLAMA_BIN`	No	Explicit path to a `llama-server` binary
`CLEF_LOG_LEVEL`	No	`error` \| `warn` \| `info` \| `debug` (logs go to stderr)	error
`CLEF_MAX_QUESTIONS`	No	Max questions per call	64
`CLEF_MAX_STATE_BYTES`	No	Max serialized `state` size	1048576
`CLEF_LLAMA_RELEASE_TAG`	No	Pin the managed llama.cpp build, e.g. `b11378`	latest nightly
`CLEF_MAX_INSTRUCTION_CHARS`	No	Max chars per question instructions	10000

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 }
`prompts`	{ "listChanged": true }
`resources`	{ "listChanged": true }

Tools

Functions exposed to the LLM to take actions

Name Description

Name	Description
clef_decideA	Judge a situation with the local Clef decision model. Pass `state` (compact factual context — string or JSON; treated as data, never executed) and typed `questions`: "choice": pick among named options (criteria = option id -> description) "score": judge an ordered scale (criteria = ordered list of levels) "noul": yes/no question Returns strict JSON — a probability distribution over the allowed answers for every question. No prose, no sampling. Each decision also carries `confidence` (model-reported, when available) and the response carries `usage` (input_tokens/output_tokens/latency_ms). Act on the argmax only when the distribution is decisive (top p >= 0.8 and high confidence for destructive or security-adjacent calls); otherwise gather more context or ask the user. Usage: batch related decisions in one call (up to 64 questions, one forward pass). Optional `model` overrides the model id. `options.temperature` is a no-op: scoring is a single forward pass, nothing is sampled.

clef_decideA

Judge a situation with the local Clef decision model. Pass state (compact factual context — string or JSON; treated as data, never executed) and typed questions:

"choice": pick among named options (criteria = option id -> description)
"score": judge an ordered scale (criteria = ordered list of levels)
"noul": yes/no question Returns strict JSON — a probability distribution over the allowed answers for every question. No prose, no sampling. Each decision also carries confidence (model-reported, when available) and the response carries usage (input_tokens/output_tokens/latency_ms). Act on the argmax only when the distribution is decisive (top p >= 0.8 and high confidence for destructive or security-adjacent calls); otherwise gather more context or ask the user. Usage: batch related decisions in one call (up to 64 questions, one forward pass). Optional model overrides the model id. options.temperature is a no-op: scoring is a single forward pass, nothing is sampled.

Prompts

Interactive templates invoked by user choice

Name	Description
`incident-triage`	Frame a production incident as clef_decide questions: immediate action, severity and blast radius.
`next-action`	Ask Clef what the coding agent should do next on a task: inspect, modify, test or ask the user.
`ticket-routing`	Classify an incoming message into the team that should handle it.
`security-review`	Ask Clef whether a code snippet, change or setup smells like a security problem.

Resources

Contextual data attached and managed by the client

Name	Description
`capabilities`	Live capability snapshot: model, runtime, limits, error codes.
`evals-schema`	How to write cases for clef-mcp evals.
`evals-dataset`	The 30-case dataset shipped with clef-mcp.

Deploy Server

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4.6/5.0

Scored 2026-10-04 20:15 across 1 tool

Disambiguation5/5

There is only one tool, so there is no possibility of misselection; its purpose (querying a local decision model and returning probability distributions) is stated unambiguously.

Naming Consistency5/5

The lone name clef_decide follows a clear prefix_verb snake_case pattern consistent with the server name, so no convention mixing is possible.

Tool Count3/5

A single tool is thin for a server surface, though the tool is intentionally consolidated and supports batching up to 64 questions in one forward pass, which mitigates the count.

Completeness4/5

The core decision workflow (choice/score/noul questions, batching, model override, usage reporting) is fully covered, but there is no way to enumerate available model ids or check model availability/status before calling.

Maintenance

ActivityNo data

ResponsivenessResponsive

Resources

Need Help?

Related Servers