Skip to main content
Glama

Add source text

flypost_add_source_text

Add pasted text as a Brain source item in a notebook, then rebuild its embeddings. Blocks until the text is genuinely searchable — the result reports how many items were embedded, so a no-op run can't read as success. Needs an existing notebook: create one with flypost_create_notebook.

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>",
      "title": "<title>",
      "text": "<text>"
    },
    "name": "flypost_add_source_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe full text content to store.
titleYes
is_own_contentNoTrue when the user wrote this themselves (affects drafting attribution).
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.5/5.0
Behavior5/5

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

Goes well beyond the annotations (which only say it is a non-readonly, non-destructive, closed-world write) by disclosing that the call blocks until embedding completes and that a no-op run is detectable via the embedded-item count. That is exactly the kind of latency and success-signal context an agent needs before invoking a synchronous mutation.

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 tightly packed sentences: what it does, how it blocks and reports, then the prerequisite. No filler, and the most decision-relevant fact (synchronous embedding) is placed early.

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?

There is no output schema, and the description compensates by explaining what the result reports (embedded-item count) and why that matters. Combined with the prerequisite and blocking behavior, an agent has everything needed for a 4-parameter write call.

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 75%, so most parameters are already documented. The description adds the meaningful constraint that source_package_id must reference a pre-existing notebook, but says nothing about text limits or how is_own_content affects behavior beyond what the schema already states. Baseline 3 is appropriate.

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?

States a specific verb and resource: 'Add pasted text as a Brain source item in a notebook, then rebuild its embeddings.' The qualifier 'pasted text' implicitly separates it from the document- and URL-based sibling add tools, and the embedding-rebuild step is named explicitly.

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?

Gives a concrete prerequisite and the exact sibling to satisfy it: 'Needs an existing notebook: create one with flypost_create_notebook.' The schema's source_package_id description also points at flypost_list_sources. It stops short of an explicit exclusion (e.g., 'use flypost_add_source_url for URLs'), so routing among the four add_source_* variants is left partly to inference.

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.