Skip to main content
Glama
bryan-protocol-mcp

bryan-protocol-mcp

by MihailoPesic

check_stance_and_changes

Check whether Bryan actively uses, has stopped, or strictly avoids a supplement, food, habit, or therapy, with rationale and chronological mentions across videos and articles.

Instructions

Check whether Bryan actively uses/does something, stopped doing it, or strictly avoids it, including rationale and chronological mentions across videos and articles.

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": "check_stance_and_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesSupplement, food, habit, or therapy (e.g. 'rapamycin', 'alcohol', 'sunscreen', 'metformin').

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?

With no annotations supplied, the description carries the full disclosure burden. It does useful work by stating the source corpus (videos and articles) and that results include rationale plus a chronological ordering, which implies a read-only retrieval rather than a mutation. It stops short of stating permissions, whether results are exhaustive or ranked, or what happens when no mentions exist.

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 that front-loads the operation and the outcome taxonomy before the return-content clause. It is dense without padding, though the phrase 'actively uses/does something' is slightly vague compared to the sharper 'stopped doing it' and 'strictly avoids it'.

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 one-parameter read tool with no output schema and no annotations, the definition covers what it does, the accepted topic domain, and the shape of the return (rationale plus chronological mentions). Only the empty-result and source-scope boundaries are left unaddressed, which is minor at this complexity.

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 description coverage is 100%, and the single parameter already documents accepted categories with examples ('rapamycin', 'alcohol', 'sunscreen'). The description adds no syntax, normalization, or naming-convention guidance beyond the schema text, so the baseline 3 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?

The description uses a specific verb ('Check') plus a well-defined resource: Bryan's stance on a topic, enumerated into three concrete outcome classes (actively uses, stopped, strictly avoids). It also states the payload ('rationale and chronological mentions across videos and articles'), which separates it in spirit from recommendation-style siblings like what_would_bryan_do, though no sibling is named outright.

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?

Usage is implied by the verb and topic parameter — an agent can infer this is for retrieving Bryan's historical position on a supplement/habit. However, there is no explicit when-to-use vs when-not guidance and no routing to alternatives such as what_would_bryan_do (advice) or get_official_protocol (formal protocol), even though those overlap closely.

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