Skip to main content
Glama

SHPBL: Repository Audit & Repair

by com.shpbl

Read a library document

library_document
Read-onlyIdempotent

Read one long SHPBL document, paged for a context window: volume (the complete text of a volume of The Strategic Master Library), catalog_outline (the Collective catalog's parts, component classes, agent-kit steps and verification axes), report_template (the branded audit report HTML to fill in), or standing_order (the prompt that governs a run). Requires a Practitioner key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoYour SHPBL subscription key (shpbl_mcp_…). Optional if your client sends it as the `Authorization: Bearer …` request header.
partNo1-based page of the document, up to 60.
volumeNoRequired for `document: volume` — the volume slug or its number, 1 through 7.
sectionNoFor `document: catalog_outline` — only parts or sections whose name contains this text.
documentYesWhich document to read.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds useful behavior beyond that: the tool pages long documents for a context window and requires a Practitioner key. There is no contradiction with the annotations.

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?

Two sentences with no filler. The main purpose is front-loaded, and the parenthetical enumerations are compact and informative.

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

Completeness4/5

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

Together with full schema coverage and read-only/idempotent annotations, the description covers document variants, paging, and auth. It does not spell out the exact return page structure, but 'paged for a context window' plus the `part` parameter is sufficient for an agent to 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 coverage is 100%, so the baseline is 3, but the description adds meaningful semantics for the document enum: volume, catalog_outline, report_template, and standing_order are each explained. It also explains the key requirement, which the schema presents as optional under certain conditions.

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?

States a specific action ('Read') on a concrete resource ('one long SHPBL document') and enumerates the four document types with brief definitions. This makes it easy to distinguish from sibling tools like library_index and library_search.

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

Usage Guidelines4/5

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

The description clearly indicates when to use the tool: when a full named document is needed, paged for a context window. It also notes the Practitioner key requirement. It does not explicitly contrast with library_index or library_search, so it stops short of full alternative guidance.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools target distinct stages or resource types: evaluate/fix/harvest are clearly separate audit phases, and write_to_repo/list_repos are unambiguous. The library_* trio is mostly separable but library_document and library_index both offer access to volumes, and run_gauntlet partially overlaps the individual stage tools, so a couple of boundaries are less crisp.

Naming Consistency4/5

Names are uniformly lowercase snake_case and mostly follow a verb_noun pattern: evaluate_repo, fix_repo, harvest_repo, write_to_repo, list_repos, run_gauntlet. A few are noun_noun or resource-prefixed like library_search, library_document, subscription_status, and welcome/selfcheck_mcp are one-offs, so it is predictable but not perfectly uniform.

Tool Count5/5

At 14 tools the server sits within the ideal 3-15 range, and each tool has a plausible role in the audit/repair, library, or operational workflow. The count is on the larger side but justified by separate free and Practitioner lanes, library services, and health/status checks.

Completeness4/5

The core audit lifecycle is well covered: list/scope, evaluate, fix, harvest, write back, plus library search and run orchestration. The main gap is that build_intent explicitly gates COMPOSE/SPECIALIZE/CREATE operations, but no actual compose/specialize/create tools are exposed, and there is no explicit run_gauntlet cancellation or reset, though agents can work around both.

Resources