Skip to main content
Glama
bryan-protocol-mcp

bryan-protocol-mcp

by MihailoPesic

what_would_bryan_do

Answers what Bryan Johnson would or wouldn't do for a habit, food, supplement, or scenario using tiered, citation-first evidence from protocol pages, articles, videos, and timestamped podcast quotes.

Instructions

Retrieve a tiered Ground Truth Dossier (explicit stances, Tier 1 protocol pages, Tier 2 Bryan videos/articles, Tier 3 external podcast timestamped quotes) to answer what Bryan Johnson would or wouldn't do in a scenario.

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": {
      "question": "<question>"
    },
    "name": "what_would_bryan_do"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesScenario, habit, food, supplement, or question (e.g. 'Should I drink coffee after noon?', 'Does Bryan take rapamycin?').
max_per_tierNo
include_transcriptsNoInclude timestamped video and podcast quotes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does real work by revealing the tiered composition of the result (explicit stances, Tier 1 protocol pages, Tier 2 videos and articles, Tier 3 timestamped external podcast quotes) and 'Retrieve' implies a read operation. It does not say what happens when no ground truth exists, whether the dossier synthesizes an answer or only aggregates sources, or anything about latency or rate limits.

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?

It is a single dense sentence with the verb and the resource front-loaded and the purpose stated at the end. The parenthetical tier enumeration is long but earns its place by defining the return contents. It could be trimmed, but it contains no filler.

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 three-parameter retrieval tool with no output schema, the crucial missing detail is what comes back, and the description addresses it by describing the dossier's tiers and contents. The main remaining gap is whether the response is a synthesized recommendation or a bundle of cited sources, which matters for how the agent should present the result.

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%: 'question' and 'include_transcripts' are documented in the schema, while 'max_per_tier' has no schema description. The description's tier breakdown indirectly explains what a per-tier cap means, but it never states that max_per_tier limits how many items come back from each tier, so the one undocumented parameter stays under-explained.

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 gives a specific verb ('Retrieve') and a specific resource ('tiered Ground Truth Dossier'), and it names the question it answers: what Bryan Johnson would or wouldn't do in a scenario. That is enough to distinguish it from get_official_protocol or check_stance_and_changes, but the description does not explicitly contrast itself with those siblings.

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

Usage Guidelines3/5

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

The intended use case is clear from 'to answer what Bryan Johnson would or wouldn't do in a scenario', which implicitly tells the agent to call this for scenario or behavior questions. However, there is no explicit guidance on when to prefer this tool over get_official_protocol or check_stance_and_changes, and no exclusions or prerequisites are stated.

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