Skip to main content
Glama
screener-mcp
by LogeshR15

notebook_ai

Destructive

Save, read, and AI-summarize investment research notes locally, with persistent symbol-specific storage for research insights.

Instructions

Save, read, and AI-summarize your investment research notes locally.

Notes are stored in ~/.screener-mcp/notebooks/ — persists across sessions.

action: "create" — new note (requires symbol + content) "append" — add to existing note (requires note_id + content) "read" — read a note (requires note_id) "list" — list all notes (optional symbol filter) "summarize" — AI-structured summary of all notes for a symbol "delete" — delete a note (requires note_id)

Examples: notebook_ai("create", symbol="TCS", content="Q3 results strong — revenue beat...") notebook_ai("append", note_id="a1b2c3d4", content="Met management — bullish on BFSI...") notebook_ai("list", symbol="TCS") notebook_ai("summarize", symbol="TCS") notebook_ai("read", note_id="a1b2c3d4")

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": {
      "action": "<action>"
    },
    "name": "notebook_ai"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
symbolNo
contentNo
note_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the on-disk location ~/.screener-mcp/notebooks/ and persistence across sessions, plus the fact that summarize invokes AI structuring. It does not state that delete is irreversible or what happens on a bad note_id, which would have raised this further.

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?

Front-loaded purpose, then a scannable action list, then examples — the right order for a polymorphic tool. The examples partly restate the action table, but for a six-mode tool that redundancy buys real error reduction, so only minor trimming is warranted.

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?

An output schema exists, so return-value explanation is not required, and storage location, persistence, and per-action parameters are all covered. Remaining gaps are edge-case behavior: whether delete is permanent, whether create overwrites an existing note for the same symbol, and how summarize handles a symbol with no notes.

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 description coverage is 0% and the schema only requires 'action', so the description carries the full burden — and it does, mapping each of symbol, content, and note_id to the specific actions that need them. The concrete invocation examples (including a sample note_id like 'a1b2c3d4') supply format hints the schema entirely lacks.

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?

Opens with a specific verb set plus resource: 'Save, read, and AI-summarize your investment research notes locally,' then enumerates all six actions. No sibling tool in the catalog handles personal notes, so the tool is unambiguously distinguishable from research/portfolio tools.

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?

The action table effectively defines when each mode applies and what each mode needs ('requires symbol + content', 'optional symbol filter'), which is strong per-mode guidance. It stops short of explicit exclusions or a statement of when not to use this tool versus, say, ask_company_research for storing findings.

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