mcp-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCPTOOLS_DB | No | Path to a SQLite file to persist the results of grade_answer and model_drift. Unset, nothing is written and the server behaves exactly as before. | |
| MCPTOOLS_CORPUS | No | Path to a notes.json corpus file (a {"id": "text", ...} file) used by the search tool. Set to point search at your own notes. |
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 |
|---|---|
| calcA | Evaluate an arithmetic expression safely (no code execution; names, calls and imports are rejected). |
| searchA | BM25 keyword search over a small bundled document corpus; returns the top matches with their scores. |
| grade_answerA | Check a draft answer against its sources and report which sentences the sources do NOT support — fabricated figures and claims the sources never make. Deterministic and lexical, not a model judgement. Call this on your own answer before giving it to the user when the answer is supposed to be grounded in provided material. |
| model_driftA | Look up how a live LLM is currently scoring on a public, frozen eval suite (accuracy, latency, answer length, reliability, refusal rate) and whether those moved since the previous weekly run. Use it to check whether a model you're about to rely on has quietly changed. Omit |
| compare_runsA | Ask whether a project's most recent stored eval run regressed against the one before it — per-case, so a better average can't hide a case that broke. |
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
Each tool has a completely distinct purpose: arithmetic evaluation, keyword search, answer grading, model monitoring, and eval comparison. No overlap in functionality.
Names are mostly descriptive and use lowercase with underscores, but there is slight inconsistency: calc and search are single words, while others follow a verb_noun or noun_noun pattern. Still very readable.
5 tools is a well-scoped set for a utility server. Each tool serves a clear, non-redundant purpose, neither too few nor too many.
The tool set covers the stated utilities (math, search, answer checking, model drift, run comparison) comprehensively for its scope. Minor gaps like source management could exist but aren't critical.