nblm-mcp

chat_history

Read past question/answer turns for a notebook's current conversation, returning the newest entries first so agents can review prior context.

Instructions

Read past question/answer turns for a notebook's current conversation.

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": {
      "notebook_id": "<notebook_id>"
    },
    "name": "chat_history"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of turns to return, newest conversation first.
`notebook_id`	Yes	The notebook whose conversation to read.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it supplies almost nothing beyond the word "Read." It does not state read-only guarantees, auth/permission requirements, ordering behavior, or what happens when the conversation is empty.

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?

A single front-loaded sentence with no filler; the resource and scope are stated in the first few words and nothing is wasted.

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?

With an output schema present, return values need not be described, and both parameters are documented. The only shortfall is the absence of any safety/behavioral note, which matters more here because there are no annotations to lean on.

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 description coverage is 100%, with both notebook_id and limit fully documented in-schema (including the newest-first ordering), so the baseline is 3. The description's "current conversation" phrasing adds only marginal scope nuance over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb ("Read") with a specific resource ("past question/answer turns") scoped to "a notebook's current conversation." That is enough to distinguish it from siblings like ask or get_notebook, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the "current conversation" framing suggests using it alongside ask to recover prior turns, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer the trigger condition.

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

Deploy Server