tero-mcp-lite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TERO_TOKENS | No | Whitespace/comma-separated token:scope list, e.g., 's3cr3t:read other:refresh'. Required unless TERO_TOKENS_FILE is set. | |
| TERO_INDEX_PATH | No | Path to the Tero index.json file. Defaults to 'docs/tero-index/index.json'. | |
| TERO_TOKENS_FILE | No | Path to a file containing the token:scope list (same format as TERO_TOKENS). |
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 |
|---|---|
| identifyB | Server identity, version, and whether the Layer-2 gate is open. |
| query_by_idA | Exact lookup by corpus id (RFC-0034, M-1015, DN-87, an issue id). |
| query_by_statusB | All rows with a given status (Accepted, todo, done, …). |
| query_by_kindB | All rows of a given kind (rfc, adr, note, issue, section, …). |
| cross_refA | Breadth-first walk of depends_on/doc_refs edges from a start id/anchor. |
| text_searchB | Ranked free-text search over id/title/summary. |
| citeD | Citations only for a query (kind + its args, as query_*). |
| explainC | EXPLAIN trace only for a query (kind + its args, as query_*). |
| refreshA | Reload the served index from disk (requires the |
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 9 tools
Each tool serves a clearly distinct purpose: citation, graph traversal, explain, identity, various queries, refresh, and text search. There is no functional overlap that would confuse an agent.
Tool names are a mix of single-word verbs (cite, explain, refresh) and multi-word patterns (query_by_id, query_by_kind). While all are readable, there is no consistent verb_noun or pattern across the set, causing moderate inconsistency.
Nine tools is an appropriate count for a knowledge base server. Each tool covers a needed operation without being excessive or sparse.
The tool set covers querying by ID, kind, status, text search, graph traversal, citation, and explain. For a read-only documentation system, this is comprehensive. Minor gaps like aggregation are acceptable.