Skip to main content
Glama
bryan-protocol-mcp

bryan-protocol-mcp

by MihailoPesic

search_archive

Search indexed Blueprint protocol pages, articles, videos, and podcast transcripts by keyword to retrieve citation-ready references and filter results by source type or tier.

Instructions

Full-text BM25 search across all official protocol pages, Blueprint blog articles, @BryanJohnson videos/streams, and external podcast transcripts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_archive"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNoOptional tier filter (1=official protocol, 2=official articles/videos, 3=external podcasts).
limitNo
queryYesSearch query.
source_typeNoOptional source type filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the ranking algorithm (BM25) and corpus breadth, which is genuinely useful, but says nothing about result format (snippets? URLs?), whether results are relevance-ranked with scores, pagination behavior, or what happens when a query matches nothing across tiers.

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?

A single front-loaded sentence with the distinctive detail (BM25, corpus scope) placed early and zero filler. It is efficient but slightly undersized for a tool with two filtering parameters and no annotations.

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

Completeness3/5

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

For a 4-parameter search tool with no annotations and no output schema, the definition covers purpose but leaves the agent guessing about return shape and result handling. Missing are any statement on what a hit contains and how to progress from search to retrieval.

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

Parameters3/5

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

Schema coverage is 75%, so the schema largely documents query, limit, and the source_type enum itself. The description's corpus enumeration loosely maps to the tier concept (official protocol/articles/videos vs. external podcasts), adding a little meaning, but it never explains the tier vs. source_type relationship or when to use the coarser filter.

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

Purpose4/5

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

Specific verb (full-text BM25 search) plus an enumerated resource scope (protocol pages, blog articles, videos/streams, podcast transcripts). An agent immediately knows this is discovery/retrieval over a defined corpus, but nothing in the text distinguishes it from retrieval siblings like get_document or get_official_protocol.

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

Usage Guidelines2/5

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

No statement of when to use this versus alternatives, no mention of following up with get_document on a hit, and no exclusions. The closest it comes is implicit: naming the corpus hints at discovery, but the agent must infer that this is the 'find' step rather than the 'fetch' step in the sibling set.

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