REFERENCE · THE TOOLS
One endpoint. A handful of verbs.
Preston speaks over a single MCP endpoint, so any MCP-capable agent can use it. The verbs group by intent: ground your agent before it writes, see what Preston holds, and steer what it does next. Reads are reflexive — never permission-gated; only request_review asks first.
Session boot for a repo you’re about to touch. One call returns the beliefs, risks, decisions, and conventions scoped to the files in play — each with a handle you can walk (why) or contest (challenge).
New to Preston? Composes a five-minute guided first session from what it already knows — a do-this-next sequence of real tool calls, not a manual.
Preston’s grounded posture before you decide or change something: prior decisions that bear on it, where beliefs conflict, the risks worth watching.
The risks Preston is holding across the workspace — code, knowledge, and project tensions — each with the finding, the evidence in plain words, what would clear it, and its severity.
Given a stable about handle, returns how a claim was observed, what it’s inferred from, whether it was ratified, and what contradicts it.
Contradictions Preston holds: scope: repo (default) finds two live claims asserting opposite polarity inside one repo; scope: org finds two repos whose conventions clash on the same dimension.
Findings the team accepted to fix later — check here before re-raising something Preston might already be holding.
The codebases Preston has climbed. A bare call lists them with state and a confidence read; pass repo to open one’s full ticket — confidence, blast radius, top risks.
orient instead when about to work in one.Preston’s PR reviews, each a ticket. A completed ticket carries the full review — verdict, comments, withheld findings, questions.
Write a settled decision (kind: decision), or a promise to fix something on a stated future trigger (kind: promise), so it persists instead of getting re-litigated.
Stop Preston from raising a whole category of findings for now — it keeps finding and counting them, just stops surfacing them.
Reverse a hold — Preston resumes raising that category on the next review. Nothing else is deleted.
Disagree with something Preston believes. Records your opposing view as a live tension against the belief — additive, never deletes it.
Endorse something Preston believes — independent support climbs a belief from a guess to corroborated.
Match a rule stated in plain words to one of the team’s standards — a correctness principle, a discipline (best practice), or a convention (taste) — in two steps: propose, then the human confirms the offer handle. Preston never adopts one on its own, and never promotes one kind into another — principle, discipline, and convention stay separate.
Starts a fresh review of a pull request. Doesn’t block — returns a pending ticket immediately; poll it with reviews.
Tell Preston’s own team something about Preston himself — a tool that didn’t exist, a shape that fought you mid-task. Not about the repo you’re working in.
every response is grounded — file · line · a recorded decision · a prior review — or it comes back empty and says why. it never invents a source. no model names, no per-call cost: what Preston does, never what it runs on.