Skip to main content
Glama

add_note

Add a note to a stream, tagging the entities it references. Reuse existing entities or create new ones.

Instructions

Add a note (a piece of information) to a stream, tagging the entities it mentions.

Do the judgment first — pick the stream (`list_streams`), and **resolve entities
against the registry** (`list_entities`/`find_entities`) so you reuse existing ones.
A change in the world is a *new* note; use `edit_note` only to fix a mistake.

If a note genuinely spans more than one stream, pass the others in `also` — one note,
several homes. **Never duplicate** a note across streams. Most notes belong to one.

Args:
    stream: Id of the primary stream (from `list_streams`).
    text: The note text.
    entities: The entities this note references. Each item is either
        {"id": "<existing-entity-id>"} (reuse) or
        {"name": str, "kind": "person|org|topic", "aliases": [str]} (create new).
    also: Additional stream ids this note also belongs in (optional).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
alsoNo
textYes
streamYes
entitiesNo
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses entity creation/reuse, multi-stream handling, and that notes represent changes in the world. Missing information on return value or permissions, but overall good transparency.

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?

Well-structured with a clear first sentence followed by workflow guidance and an Args section. Every sentence adds value without redundancy. Concise yet comprehensive.

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

Completeness4/5

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

Given no output schema, the description does not explain the return value (e.g., note ID). However, it covers usage, parameters, and behavioral context adequately. Slight omission of error handling or success response.

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

Parameters5/5

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

Schema coverage is 0%, so description must compensate. It fully explains all parameters: stream (primary), text (note content), entities (with format for reuse or creation), and also (additional streams). Adds significant meaning beyond 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?

The description clearly states the action ('Add a note to a stream') and specifies additional behavior ('tagging the entities it mentions'). It distinguishes from siblings by contrasting with edit_note (fix mistake) and implying that notes are for new information, not duplicates.

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 guidance on when to use this tool vs edit_note, instructions on entity resolution (list_entities/find_entities), and rules against duplication. The 'also' parameter usage is explained for multi-stream notes.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/praveen-ilangovan/pensieve'

If you have feedback or need assistance with the MCP directory API, please join our Discord server