Skip to main content
Glama
bryan-protocol-mcp

bryan-protocol-mcp

by MihailoPesic

get_official_protocol

Look up authoritative Tier 1 protocol sections by topic from protocol.bryanjohnson.com, returning official matches with optional full Markdown content.

Instructions

Look up authoritative Tier 1 sections from protocol.bryanjohnson.com for a given topic (e.g. sleep, nutrition, exercise, skin, oral care, hair, biomarkers, rx).

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": {
      "topic": "<topic>"
    },
    "name": "get_official_protocol"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
topicYesProtocol topic or keyword to look up.
include_full_contentNoInclude full Markdown text of top official matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden; 'look up' plus a fixed source domain reasonably implies a read-only, authoritative-source retrieval. It adds provenance value by naming protocol.bryanjohnson.com and the 'Tier 1' authority tier. It says nothing about match ordering, behavior when a topic has no match, or rate/access constraints, so gaps remain for an unannotated tool.

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 sentence, front-loaded with the action and source, with the topic examples earning their place as query-shaping aid. No filler or redundancy. Minor cost is the unexplained 'Tier 1' term, which adds words without adding shared meaning.

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 3-parameter, unannotated, output-schema-less retrieval tool, the definition covers what it fetches and from where but not what comes back, how results are ranked or truncated, or what an empty result means. It is adequate to attempt a call but not to predict the response shape.

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 67%, so the topic, limit, and include_full_content parameters are partly documented in the schema already. The description's value-add is the parenthetical topic taxonomy (sleep, nutrition, exercise, skin, oral care, hair, biomarkers, rx), which genuinely helps keyword formulation. It says nothing about how limit interacts with 'top official matches' or what 'full Markdown text' entails beyond the schema wording.

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?

The description names a specific verb ('look up'), a specific resource ('authoritative Tier 1 sections from protocol.bryanjohnson.com'), and scopes it to a topic with concrete examples (sleep, nutrition, biomarkers, rx). It is distinguishable from generic siblings like get_document or search_archive, though it never explicitly contrasts itself with them. The undefined jargon 'Tier 1 sections' slightly blunts precision.

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?

It conveys only implicit usage ('for a given topic'), with no statement of when to prefer it over get_protocol_overview, get_document, search_archive, or check_stance_and_changes. There are no exclusions, prerequisites, or fallback guidance. An agent has to infer routing from the phrase 'authoritative Tier 1' alone.

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