Skip to main content
Glama
bryan-protocol-mcp

bryan-protocol-mcp

by MihailoPesic

list_sources

Browse ingested documents, articles, videos, and podcasts with pagination and optional tier or source-type filters to find relevant archive sources.

Instructions

List ingested documents, articles, videos, and podcasts with pagination and optional tier/source_type filters.

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

Input Schema

NameRequiredDescriptionDefault
tierNo
limitNo
offsetNo
source_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that results are paginated and filterable, implying a read-only listing, but says nothing about result ordering, what metadata each entry contains, or whether the listing is scoped or permission-gated.

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, naming the resource set first and the filtering capabilities second. It is efficient, though the density leaves several terms unexplained.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four optional parameters, zero schema descriptions, no annotations, and no output schema, the definition should explain the return shape and default ordering to be callable with confidence. It stops at naming capabilities, leaving the agent to guess what a listed item looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, yet it only names "tier" and "source_type" as filters and nods at pagination without explaining what a tier means or what distinguishes the twelve source_type values. The limit/offset pairing is never clarified beyond the generic word "pagination."

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 ("List") on a concrete resource set ("ingested documents, articles, videos, and podcasts"), so an agent can tell this enumerates the corpus rather than fetching a single item. It does not explicitly differentiate itself from siblings like search_archive or get_document, leaving that distinction implicit.

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?

There is no statement of when to use this tool versus search_archive or get_document, and no prerequisites or exclusions. An agent must infer that this is the browsing/enumeration path while search_archive is the query path, which is exactly the guidance the description should supply.

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