Skip to main content
Glama

Create Note

create_note

Use when the user says to note, remember, jot down, or keep track of something that is not ready to publish — a decision, a fact, a draft, a list. First call list_notes: if a related note already exists, prefer append_note over creating a duplicate. Each call creates one separate private note. Subject to the plan note quota.

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": {
      "content": "<content>"
    },
    "name": "create_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoOptional note title
contentYesThe full note content (Markdown)

Output Schema

NameRequiredDescriptionDefault
idYes
titleYes
sourceYes
contentYes
created_atYes
updated_atYes
agent_accessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write semantics and non-idempotency are covered structurally. The description still adds real context beyond them: one note per call (no batching), notes are private, and a plan-level note quota exists. It stops short of saying what happens when the quota is hit or whether a failed call leaves partial state, which keeps it off a 5.

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 sentences, front-loaded with the trigger vocabulary an agent is most likely to match against user intent, then the workflow rule, then the creation semantics and quota caveat. No sentence repeats the name/title or restates schema fields.

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 annotations covering the safety profile and an output schema covering return values, the description only needs to carry selection and workflow guidance, which it does thoroughly. The remaining gap is edge-case behavior on quota exhaustion and whether the duplicate check is scoped to titles or content.

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% and both parameters (title, content) are documented in the schema, including the Markdown format for content, so the description has little to add. It does not clarify title behavior — for example whether titles participate in the duplicate check that drives the append_note routing — so the baseline of 3 is appropriate.

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 names the resource and the act explicitly ('Each call creates one separate private note') and anchors it to concrete user phrasings ('note, remember, jot down, or keep track of'). It also distinguishes the tool from its nearest siblings, list_notes and append_note, so an agent can pick it without opening another 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?

It gives an explicit when-to-use condition ('something that is not ready to publish — a decision, a fact, a draft, a list') plus a mandatory pre-step ('First call list_notes') and a routing rule to a named alternative ('prefer append_note over creating a duplicate'). Both the selection condition and the exclusion path are stated.

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.