Skip to main content
Glama

List Brain sources

flypost_list_sources
Read-only

List the project's Brain sources and notebooks (content_source_packages) with item counts and ingestion status.

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

Input Schema

NameRequiredDescriptionDefault
statusNo
project_idNoProject id; omit for the active project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds meaningful context by saying each entry includes item counts and ingestion status, which tells the agent what to expect in the response. It does not mention pagination, result caps, or whether archived sources are included, which is the remaining behavioral 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?

One front-loaded sentence with no filler, and the resource plus return payload appear before any qualifiers. The parenthetical internal type name is mildly jargon-heavy but earns its place by disambiguating what a 'source' actually is.

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 two-parameter, read-only list tool with no output schema, the definition covers the resource and the shape of each returned item reasonably well. It leaves unanswered whether the list is paginated or bounded and whether the status parameter filters or merely reflects state, so it is adequate but not complete.

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 50%: project_id is documented in the schema as 'omit for the active project', while status has only an enum and no description. The description partially compensates by tying 'ingestion status' to the domain, making the ready/processing/failed enum self-evident, but it never states that status acts as a filter, so the parameter's filtering behavior must be inferred.

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 names a specific verb ('List') and a specific resource ('Brain sources and notebooks'), and disambiguates the domain term by mapping it to the internal type 'content_source_packages'. It also previews what each item carries (item counts, ingestion status). It does not explicitly contrast with nearby siblings like flypost_search_brain or the other list_* tools, so it stops short of a 5.

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 explicit when-to-use guidance and no exclusions; the agent must infer that this is the browse-all entry point rather than flypost_search_brain or flypost_list_projects. Nothing states prerequisites (e.g., whether a Brain/project must exist) or when the active-project default applies.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.