Skip to main content
Glama

SHPBL: Repository Audit & Repair

by com.shpbl
OverviewDiscussionsAdmin

Search the capability library

library_search
Read-onlyIdempotent

Search the Collective Master Library for a capability in plain words, before writing new code. scope: "catalog" (Practitioner) searches the engineered components — class, what each does, API surface, line counts, verification marks. scope: "composites" searches capabilities earlier runs invented for one host by fusing library parts, each citing its sealed report. Pass ids for whole rows by component ID, with siblings and declared twins. Multi-word queries match term by term and rank; with no exact hit you get the closest rows, labelled as such.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoUp to 20 component IDs (e.g. `STIER-S-84`, `BLD-ENG-303`) returned in full instead of a search.
keyNoYour SHPBL subscription key (shpbl_mcp_…). Optional if your client sends it as the `Authorization: Bearer …` request header.
packNoVault only: restrict to one vertical pack, e.g. `fintech-v1`. Substring match.
pageNo1-based page of results. A page past the end is refused, never returned empty.
limitNoAlias for `page_size`, 1 to 50. Given both, `page_size` wins.
queryNoPlain-words capability, name, ID or API symbol. Omit to page the whole pool.
scopeNo`catalog` — engineered components (Practitioner). `crown-jewels` — the S-Tier Vault of standalone lab-curated artifacts. `composites` — capabilities past runs invented for one host. (`vault` is no longer available; asking for it returns a pointer to these scopes.)catalog
page_sizeNoRows per page, 1 to 50. Defaults to 20.
certified_onlyNoCrown jewels only: return only rows whose body the certification harness executed and read clean (CERTIFIED or PROVISIONAL). This withholds the INCONCLUSIVE rows — bodies the harness could not exercise, which still exist and still ship. Leave this off (the default) to see them too; the withheld figure is reported as `certification.withheldInconclusive`.
component_classNoCatalog only: restrict to one component class, e.g. `CrownJewel/S-Tier`, `Block/Engine`. Substring match.
include_siblingsNoWith `ids`: also list up to 12 other component IDs in the same class, for comparison.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / scope / description
      Previous value: -"`catalog` — engineered components (Practitioner). `vault` — discovery-engine pipelines. `crown-jewels` — the S-Tier Vault of standalone lab-curated artifacts. `composites` — capabilities past runs invented for one host."New value: +"`catalog` — engineered components (Practitioner). `crown-jewels` — the S-Tier Vault of standalone lab-curated artifacts. `composites` — capabilities past runs invented for one host. (`vault` is no longer available; asking for it returns a pointer to these scopes.)"
  2. Changed2 schema fields changed
    • removedInput schema / properties / page_size / default
      Removed value: -20
    • changedInput schema / properties / page_size / description
      Previous value: -"Rows per page, 1 to 50."New value: +"Rows per page, 1 to 50. Defaults to 20."
  3. Changed1 schema field changed
    • changedInput schema / properties / certified_only / description
      Previous value: -"Crown jewels only: return only rows whose body the certification harness executed and read clean (CERTIFIED or PROVISIONAL). Declared, uncertified and failed rows are withheld."New value: +"Crown jewels only: return only rows whose body the certification harness executed and read clean (CERTIFIED or PROVISIONAL). This withholds the INCONCLUSIVE rows — bodies the harness could not exercise, which still exist and still ship. Leave this off (the default) to see them too; the withheld figure is reported as `certification.withheldInconclusive`."
  4. Changed1 schema field changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Alias for `page_size`, 1 to 50. Given both, `page_size` wins.",
+  "type": "number"
+}
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds useful behavioral detail: multi-word queries match term by term, rank results, and return closest rows labelled as such when there is no exact hit. It also clarifies that composites cite a sealed report.

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

Conciseness4/5

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

The description is compact and front-loaded with the core purpose, and each sentence earns its place by explaining either search intent, scope behavior, ids, or matching semantics. It is dense but not bloated, with only minor brand-specific jargon like 'Collective Master Library'.

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?

For a no-output-schema tool with 11 parameters, the description covers the most decision-relevant behavior: when to search, which scope to choose, and how no-exact-hit results are labelled. It does not spell out the full result row shape or crown-jewels specifics, but the rich schema and annotations fill most remaining gaps.

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 schema already documents every parameter; the baseline is 3. The description adds genuine semantic value by explaining plain-words matching, ids returning whole rows with siblings and declared twins, and the meaning of the catalog/composites scopes.

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 first sentence uses a specific verb-resource pair ('Search the Collective Master Library for a capability in plain words, before writing new code') and the rest of the description explains distinct scope variants. This clearly separates it from the build/compose siblings and from library_document/library_index.

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?

It explicitly tells the agent to search before writing new code and explains when to pass ids versus a plain-word query, plus what each scope returns. It does not name alternative tools explicitly, but the context is strong enough to route an agent to the right call.

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