Skip to main content
Glama

Create Brain notebook

flypost_create_notebook

Create a Brain notebook (a source collection) and optionally seed it with pasted text items. Returns its source_package_id — the id every other source tool needs. Blocks until the seeded items are searchable, and reports how many were embedded. FIRST call flypost_list_sources: a notebook is a TOPIC collection the user picks to scope a brainstorm, so add items to a fitting existing notebook with flypost_add_source_text instead of creating a near-duplicate. Only create one when the topic is genuinely new, and seed it with every item you have rather than one notebook per snippet. Material you are supplying to back a specific idea needs no notebook at all — pass it on flypost_save_idea/flypost_save_concept and it is filed into your own Source automatically.

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": {
      "title": "<title>"
    },
    "name": "flypost_create_notebook"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoOptional text items to seed the notebook with.
titleYesNotebook name, as it will appear in the Notebooks tab.
project_idNoProject id; omit for the active project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say it is a non-destructive, non-open-world write. The description adds behavior an agent cannot infer: the call blocks until seeded items are searchable, it reports the embedded count, and it returns source_package_id that every other source tool requires — a genuinely load-bearing dependency fact.

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?

Purpose and return value are front-loaded, then the routing rules follow in a coherent order. It runs long for a three-parameter tool, but nearly every clause carries decision-relevant information; only the 'topic collection the user picks to scope a brainstorm' framing is slightly discursive.

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 write tool with no output schema, the description discloses the returned id, the blocking/searchability behavior, and the embedded count, plus enough routing context to prevent duplicate notebooks. Nothing an agent needs to invoke this correctly is missing.

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 goes beyond it by constraining how the 'items' array should be used (batch all items into one notebook rather than spreading snippets across calls), which the schema itself does not convey; title and project_id are left to the schema.

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 ('Create a Brain notebook (a source collection)'), clarifies the abstract term 'Brain notebook', and immediately gives the return value. It also separates the tool from the two nearest neighbors (flypost_add_source_text, flypost_save_idea/concept) so an agent can pick without opening a schema.

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

Usage Guidelines5/5

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

Explicit when-not and alternatives: check flypost_list_sources first, add to an existing notebook with flypost_add_source_text rather than creating a near-duplicate, and route idea-backing material to flypost_save_idea/flypost_save_concept with no notebook at all. It also gives a batching rule ('seed it with every item you have rather than one notebook per snippet').

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.