Skip to main content
Glama

Add a document to the Brain

flypost_add_source_document

Upload a document the user gave you (PDF, Word .docx, PowerPoint .pptx, .txt or .md; max 20MB) into a Brain notebook, as the notebook upload in the app does. Blocks while the text is read and indexed (usually under a few minutes) and reports whether it became searchable; a scanned PDF has no text and fails. Needs an existing notebook: create one with flypost_create_notebook. Only upload files the user actually gave you.

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": {
      "source_package_id": "<source_package_id>",
      "file_name": "<file_name>",
      "file_base64": "<file_base64>"
    },
    "name": "flypost_add_source_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoDefaults to the file name.
file_nameYesIncluding the extension, e.g. "pricing-deck.pptx".
file_base64YesBase64-encoded file bytes (no data: prefix).
is_own_contentNoTrue when the user wrote this themselves.
source_package_idYesNotebook id from flypost_create_notebook or flypost_list_sources.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare it as a non-read-only, non-destructive, closed-world write; the description adds the behavior that matters: it blocks while text is read and indexed, typically minutes, reports whether the content became searchable, and fails on scanned PDFs with no text layer. The 20MB limit and "as the notebook upload in the app does" equivalence give the agent a concrete mental model of the side effect.

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?

Three dense sentences, front-loaded with the action and formats, then blocking/failure behavior, then the prerequisite and guardrail. Nothing repeats the name or title, and every clause carries operational information.

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

Completeness5/5

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

For a mutation tool with no output schema, it covers prerequisites, blocking duration, success signal (whether it became searchable), and a known failure mode. An agent has everything needed to decide to call it and to set expectations for the user while it runs.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above that by adding constraints the schema does not carry — the accepted file types and 20MB cap that bound file_name and file_base64. It does not discuss title or is_own_content, but the schema already documents both (title defaults to file name).

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 gives a specific verb and resource ("Upload a document ... into a Brain notebook") plus the accepted formats and size cap, which implicitly separates it from the text and URL siblings. An agent can tell this is the file-bytes path into a notebook without opening the schema.

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 states a hard prerequisite ("Needs an existing notebook: create one with flypost_create_notebook") and an explicit constraint ("Only upload files the user actually gave you"). It stops short of naming flypost_add_source_text or flypost_add_source_url as the alternatives for non-file content, leaving that routing to inference from the format list.

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.