Skip to main content
Glama

SHPBL: Repository Audit & Repair

by com.shpbl
OverviewDiscussionsAdmin

Run the full gauntlet — Practitioner

run_gauntlet
Read-onlyIdempotent

One runner for an entire SHPBL repository audit and repair: survey, opening library comparison, evaluation, repair, the batched harvest, closing library comparison, the branded HTML report, and the write-back path. STRICT SEQUENCE: call it once with no step for the run card, then step: 1, step: 2, one step per turn, in order. Do the returned step, report one line to the person, then call the next. Never call two steps in one turn, never attempt the whole run at once, and never infer a finding you were not handed. From step: 2 on you must pass ledger_digest; every 3 steps (adjustable with checkpoint_interval, max 10, only when the person asks for fewer pauses) the run pauses and you must ask the person before continuing, then pass continue_ack: "continue". The final step hands over the report template and the write-back path. Your own model does all reading and writing. This full conductor requires a Practitioner key (7-day free trial). The free lane provides repository evaluation, not a partial or full gauntlet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoYour SHPBL Practitioner subscription key (shpbl_mcp_…). Optional if your client sends it as the `Authorization: Bearer …` request header.
repoYesA GitHub repository: `owner/repo`, a URL, or `owner/repo#branch`.
stepNo0 to 2000. 0 (default) returns the run card and the plan with no source. 1…N walk the harvest batches, one per turn and in order. N+1 closes the run with the report template and the write-back path. Do not skip ahead.
budgetNoCharacters per harvest step — a whole number from 10,000 to 120,000. Defaults to a moderate 45,000 so each step stays readable and cheap; raise it toward 90,000 only if the person asks for fewer, heavier steps.
includeNoOptional path filter — only paths containing this text are in scope for the whole run.
fold_tokenNoThe `fold_token` returned by the previous step, passed back verbatim. Required from `step: 2` onward: it is signed by this server and carries the previous step's number and the hash of the ledger you held then, so a step cannot be skipped and a ledger cannot be truncated or replaced. Never edit it, never write one yourself.
own_libraryNoYour own previously harvested capabilities, read out of your repository's `.shpbl/` library and passed back in. Optional. When present, this run checks your concerns against your own library first and tells you which ones you already solved. It is held in memory for this call only — never stored, never added to SHPBL's library.
personalityNoHow the person wants to be spoken to for this run: technical, professional, friendly, light, coach, deadpan. Ask them once before step 0 and pass what they choose; it rides the run and changes wording only, never a finding, a state or a gate. Defaults to professional when they have no preference. Pass `none` to switch the voice off entirely — bare wording, no openers, no asides — which is the right setting for an automated reviewer reading the run as evidence.
continue_ackNoThe person's approval to continue past a checkpoint. Every 3 harvest steps this run pauses: report to the person, ask whether to continue, and only when they say yes call the next step with `continue_ack: "continue"`. Never send it without asking.
github_tokenNoOptional GitHub token (Contents: read) for a private repository. Not needed if the SHPBL GitHub App is connected to this key.
protocol_ackNoSet true to say this session already holds the SHPBL protocol. The discipline, the ten meta capabilities, the hands-off list and the return shapes are then not printed on step 0 or step 1 — they are unchanged and they still bind the run. Use it when you have already called `method_protocol` or run a staged tool in this session; it saves tens of thousands of characters of repetition.
ledger_digestNoThe ledger folded so far, one line per capability, **each line carrying the file path it came from** (for example `src/lib/queue.ts — retry with backoff`). Required from `step: 2` onward — it is the proof that you actually folded the previous step — and required on the closing step so the closing library comparison runs against what you harvested. The server checks shape as well as length: a ledger that names no paths, or is padded out around one, is refused (and not charged).
checkpoint_intervalNoHow many harvest steps between check-ins with the person. Defaults to 3; raise it (up to 10) only when the person has asked for fewer pauses. Never set it silently — the check-ins are how the person stays in the loop. Once set it rides inside the run's `fold_token`, so passing it again on later steps is not required; if you ever start a fresh chain, set it again or the run returns to 3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / personality / description
      Previous value: -"How the person wants to be spoken to for this run: technical, professional, friendly, light, coach, deadpan. Ask them once before step 0 and pass what they choose; it rides the run and changes wording only, never a finding, a state or a gate. Defaults to professional when they have no preference."New value: +"How the person wants to be spoken to for this run: technical, professional, friendly, light, coach, deadpan. Ask them once before step 0 and pass what they choose; it rides the run and changes wording only, never a finding, a state or a gate. Defaults to professional when they have no preference. Pass `none` to switch the voice off entirely — bare wording, no openers, no asides — which is the right setting for an automated reviewer reading the run as evidence."
  2. Changed1 schema field changed
    • addedInput schema / properties / personality
      Added value: +{
+  "description": "How the person wants to be spoken to for this run: technical, professional, friendly, light, coach, deadpan. Ask them once before step 0 and pass what they choose; it rides the run and changes wording only, never a finding, a state or a gate. Defaults to professional when they have no preference.",
+  "maxLength": 40,
+  "type": "string"
+}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With annotations already carrying readOnlyHint, openWorldHint, and idempotentHint, the description adds substantial behavioral context beyond them: the server signs fold_token to prevent step skipping or ledger replacement, checkpoints halt the run pending human approval, the server validates and refuses malformed ledgers ("and not charged"), and own_library is held in memory for this call only. The clause "Your own model does all reading and writing" resolves the apparent tension between readOnlyHint and the repair/write-back mention — no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Though long, every sentence carries a distinct operational rule for a genuinely complex 13-parameter, multi-turn conductor. It is front-loaded with purpose and the step sequence, uses caps judiciously for hard prohibitions, and orders sections logically: purpose, sequence, gates, credential caveat. This density is justified by the tool's complexity rather than being padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter tool with no output schema, the description is remarkably complete: it covers the full call protocol across turns, per-step parameter requirements, checkpoint gates and human-in-the-loop behavior, auth thresholds and billing nuance, sibling differentiation, and what the final step hands over. The schema covers the run-card return value ("0 returns the run card and the plan with no source"), so nothing essential is missing for an agent to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the schema already documents each parameter in detail. The description adds genuine lifecycle semantics the schema cannot express: ledger_digest and fold_token become mandatory from step 2 onward, checkpoint_interval "rides inside the run's fold_token" and persists across steps, and personality is to be asked once before step 0. This temporal inter-parameter guidance meaningfully supplements the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource — "One runner for an entire SHPBL repository audit and repair" — and enumerates the full phase list (survey, opening library comparison, evaluation, repair, batched harvest, closing comparison, HTML report, write-back). It distinguishes itself from its siblings by being the full-sequence conductor, noting that the free lane provides "repository evaluation, not a partial or full gauntlet," which cleanly separates it from evaluate_repo, fix_repo, and harvest_repo.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit, imperative usage rules: call once with no step for the run card, then step: 1, step: 2, one step per turn in order; explicit prohibitions ("Never call two steps in one turn, never attempt the whole run at once"); and conditional rules stipulating when ledger_digest and continue_ack are required. It also states the when-not: the Practitioner key requirement and the free lane's limitation to evaluation only, so an agent knows not to invoke the full conductor without the key.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SHPBL: Repository Audit & Repair toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources