Skip to main content
Glama

Create a notebook

create_notebook

Create a private persistent notebook and get its secret token. Use it as long-term memory across sessions: notes are kept for 30 days after the last use. Store the token yourself; it cannot be recovered.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_notebook"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, non-idempotent, non-destructive local operation, and the description adds genuinely useful behavior: a 30-day retention window measured from last use, and the fact that the token cannot be recovered. That is valuable beyond the annotations, but it leaves open whether repeated calls create duplicate notebooks and what happens to notes after expiry.

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 short sentences, front-loaded with the action and result, then the lifecycle rule, then the critical warning. Nothing is padded and each sentence carries distinct information.

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 zero-argument creation tool with no output schema, the description covers what is produced (a secret token), how long data survives (30 days after last use), and the one irreversible failure mode (unrecoverable token). An agent has everything it needs to call and handle this correctly.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate. Baseline 4 applies for a zero-parameter 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?

States a specific verb and resource ("Create a private persistent notebook") plus the return value ("its secret token"), which is more than the title restates. It does not name or explicitly contrast with siblings such as write_note/read_notes, so differentiation is only implied through the long-term-memory framing.

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?

"Use it as long-term memory across sessions" tells the agent the situation this tool is for, which is real usage guidance. It stops short of stating when not to use it or naming an alternative mechanism for ordinary note storage.

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.