Skip to main content
Glama
tendboat-mcp

tendboat-mcp

Official
by tendboat

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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.

spec is what the source says, verbatim: a container path (/entry.sh), a command line (python3 app/ingest.py), an HTTP path (/api/lookup), or a fully-qualified name. One call per boundary, no guessing.

Naming the gid is the whole point: free-form addresses written on two sides independently are not a stable join key. Returns no target indexed for ... when nothing in this repository serves it -- that answer is correct and useful: it means the peer is outside, and the boundary should say so rather than name a gid.

read_linesA

Read a slice of a repo file, 1-indexed and inclusive, returned with a NNNN| line-number margin. Use those numbers verbatim for Loc.line -- they are the file's own numbering. At most 400 lines per call.

search_repoA

Regex over file contents; path:line: text per hit. path_glob is REQUIRED -- name the file or directory you mean.

For rare identifiers, not for common tokens: a query like \btrue\b matches hundreds of lines, you get the first few, and you learn nothing. The hit COUNT is always reported so a bad query is visible as such. Literals, call sites and config settings are already in your prompt -- this tool is for what is not.

tendboat_indexA

Build the deterministic whole-repo index for repo (absolute path of the repository you are working in). Once per repository, again after a large checkout change. No model.

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. path is relative to repo; omit part to receive the next missing size-bounded part automatically.

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 repo -- name the files at the OTHER end of what they touch, and say which are already described. A flow with one end described and the other not is found by nothing, and the silence looks like a clean result.

tendboat_solveB

Compose everything stored for repo and return the findings, each with a short id. Deterministic, ~1s, safe at any point. Says how many findings earlier triage hid; include_suppressed prints those with their reasons.

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_solve still FINDS everything and hides what you judged false, saying how many it hid. A false positive means tendboat read the code wrong, and needs a reason from a closed list. A verdict dies when the line it was about changes.

tendboat_pathsA

What already-known taint flows touch this file, or this line. Answers from stored state; asks nothing of you. path is relative to repo.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 12 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.