tendboat-mcp
OfficialServer 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_symbolA | Resolve a class/function/method NAME to its definition and CANONICAL gid. Use the gid this returns for Call.target.gid: it is the id the analyzer joins on, so a guessed format silently fails to link. |
| resolve_targetA | Resolve what a CROSS-BOUNDARY call launches into the gid of its entry point. Use the gid this returns as the boundary target.
Naming the gid is the whole point: free-form addresses written on two
sides independently are not a stable join key.
Returns |
| read_linesA | Read a slice of a repo file, 1-indexed and inclusive, returned with a
|
| search_repoA | Regex over file contents; For rare identifiers, not for common tokens: a query like |
| tendboat_indexA | Build the deterministic whole-repo index for |
| tendboat_viewA | The file as tendboat sees it: a numbered listing with resolved callee gids,
entry points and deploy mappings attached to their lines. Says what to
send next, and carries the rules for filling it. Call before describing
any file. |
| tendboat_put_structB | Store one file's STRUCTURE as JSON: functions, call sites, dataflow edges. No security judgement. Pass through the part number requested by tendboat_view. Rejects with the exact validation errors. |
| tendboat_put_judgeB | Store one file's SECURITY assertions as JSON: sources, sinks, sanitizers, contracts, dangerous constants. Needs its structure stored first. Rejects with the exact validation errors. |
| tendboat_scopeB | Given the files you are about to judge -- a commit, a diff, a handful
of paths relative to |
| tendboat_solveB | Compose everything stored for |
| tendboat_triageA | Record what your review decided: a JSON list of
{"id","verdict","severity"|"fp_reason","evidence"}; a
sanitizer-present FP also needs evidence_loc="path:line". The next |
| tendboat_pathsA | What already-known taint flows touch this file, or this line. Answers
from stored state; asks nothing of you. |
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 12 tools
Each tool occupies a distinct slot in a staged pipeline (index -> view -> put_struct -> put_judge -> solve -> triage), and the descriptions actively draw boundaries, e.g. search_repo is 'for what is not' already in the prompt and tendboat_paths 'answers from stored state; asks nothing of you'. The main soft spots are lookup_symbol vs resolve_target (both 'resolve X to a gid', differing only in input domain) and tendboat_scope vs tendboat_paths vs tendboat_solve, which all reason about cross-file reachability and require careful reading to keep apart.
All twelve names are snake_case verb_noun (lookup_symbol, read_lines, search_repo, put_struct, put_judge, solve, triage), so the surface reads predictably. The only deviation is the arbitrary split between eight tendboat_-prefixed tools and four bare ones, which does not map cleanly onto any stated distinction since lookup_symbol and resolve_target are just as domain-specific as the prefixed tools.
Twelve tools is squarely in the well-scoped range, and each maps to a real step in the workflow rather than a redundant variant. Nothing looks like padding: the three 'resolve/read/search' utilities, the index/view pair, the two put_* writers, and the scope/solve/triage/paths analysis loop all have a job.
The lifecycle is well covered: index build, file inspection, structure and security storage, scope expansion, solve, and triage verdicts, plus symbol/boundary resolution and raw file access. The gaps are administrative rather than blocking: no tool to invalidate or delete stale stored state, no way to list indexed repos or per-file progress, and no way to revoke a triage verdict except by touching the line it refers to.