Skip to main content
Glama
bryan-protocol-mcp

bryan-protocol-mcp

by MihailoPesic

get_protocol_overview

Retrieve database statistics, source tiers, last-ingested metadata, and an index of official Tier 1 protocol sections to verify coverage and locate authoritative references.

Instructions

Get database stats, source tiers, last-ingested metadata, and the index of all official Tier 1 protocol.bryanjohnson.com sections.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_protocol_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does communicate that the payload is aggregate metadata (stats, tiers, ingestion timestamps, a section index) rather than document content, which meaningfully sets expectations. It does not state that the call is side-effect free, whether results are cached, or how large the index may be, which for a zero-annotation tool leaves some gap.

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 no filler or preamble. The four returned artifacts are listed compactly, though the final clause ('index of all official Tier 1 protocol.bryanjohnson.com sections') is dense and could read more cleanly as a separate clause.

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?

There is no output schema and no parameters, so the description's main job is to preview the return payload, and it does that by naming the four data groups. The only shortfall is that it does not warn how the embedded section index relates to the sibling retrieval tools, leaving a small ambiguity for an agent planning a multi-call sequence.

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?

The tool takes no parameters and the schema is empty with additionalProperties=false, so there is nothing for the description to clarify. The baseline for a zero-parameter tool applies.

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?

Names a specific verb (Get) and enumerates the resources returned: database stats, source tiers, last-ingested metadata, and an index of Tier 1 protocol sections. That is clearly more than a restatement of the name. It does not, however, distinguish itself from siblings like get_official_protocol or list_sources, which appear to overlap with the 'index of all official Tier 1 sections' portion.

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 word 'overview' plus the enumeration of aggregate metadata implies this is an orientation/first-call tool rather than a content-retrieval tool, but the description never says when to prefer it over get_official_protocol, list_sources, or search_archive. Usage must be inferred from the noun 'overview' alone.

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