Skip to main content
Glama
bryan-protocol-mcp

bryan-protocol-mcp

by MihailoPesic

get_document

Fetches the full text of a document by ID from search or source lists, with optional timestamped segments for videos and podcasts.

Instructions

Fetch the full text (and optionally timestamped segments) of any document ID returned by search or list_sources.

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": {
      "doc_id": "<doc_id>"
    },
    "name": "get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesDocument ID (e.g. 'protocol:sleep', 'article:why-i-avoid-the-sun', 'yt:coU8aHzTvpk').
max_charsNo
include_segmentsNoInclude individual timestamped video/podcast segments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry full behavioral burden. It discloses that the tool fetches full text and optionally timestamped segments, but it does not explain truncation behavior, error handling for missing documents, or authentication/rate-limit expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted wording. It puts the core action and scope first, then adds the optional segment behavior without distracting detail.

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 simple read/fetch tool with no annotations and no output schema, the description covers the main action and doc_id provenance. However, it omits important context around max_chars truncation and what the returned text and segments look like, leaving some operational gaps.

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 some parameter documentation exists. The description adds useful meaning for doc_id by tying it to search or list_sources and clarifies include_segments as optional timestamped segments, but it leaves max_chars and its truncation implications unexplained.

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

Purpose5/5

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

The description states a specific verb and resource: fetch the full text and optional timestamped segments of a document. It also scopes the tool to document IDs returned by search or list_sources, which distinguishes retrieval by known ID from discovery tools.

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

Usage Guidelines4/5

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

It clearly implies when to use the tool: after obtaining a document ID from search or list_sources. It does not explicitly state when not to use it or name alternative retrieval tools, but the provenance guidance is enough for correct selection in most cases.

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