Skip to main content
Glama

Coline

Write a note

create_note

Creates a note: plans, drafts, summaries, meeting notes, working notes. Write the body in markdown; the person sees the page take shape inside the chat and can edit it there.

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

Input Schema

NameRequiredDescriptionDefault
bodyNoMarkdown: headings, lists, checklists, quotes, code.
titleNo
blocksNoColine's note blocks, instead of a markdown body. Rarely needed.
driveIdNoDrive to put it in; default: the person's default writable drive.
parentIdNoFolder to put it in, in that drive.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
urlYes
bodyYes
titleYes
noteIdYes
revisionYes
bodyTruncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world behavior, so the bar is lower. The description still adds real behavioral context beyond them: the page materializes live in the chat and the human can edit it there, which tells the agent this is a visible, collaborative creation rather than a silent write. It stops short of stating permissions, limits, or what happens if a same-titled note exists.

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?

Two sentences, front-loaded with the verb and resource, then the markdown instruction and the live-preview behavior. No filler or repetition. The content-type list is slightly long but earns its place by scoping the tool's intended use.

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?

For a six-parameter creation tool with an output schema and 83% schema coverage, the description supplies the pieces the schema cannot: what the tool is for and that the result is human-visible and editable. Placement semantics (driveId, parentId defaults) are left entirely to the schema, which is an acceptable division of labor here.

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 coverage is high (83%), so the schema already explains body as markdown, blocks as the rare alternative, driveId as the target drive, and parentId as the folder. The description's "write the body in markdown" largely restates what the schema says, adding only mild emphasis. With the schema doing the heavy lifting, a baseline 3 is appropriate.

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 ("Creates a note") and enumerates the content it is meant for: plans, drafts, summaries, meeting notes, working notes. That makes the tool's job unambiguous. It does not, however, differentiate itself from nearby siblings such as save_note, create_doc, or update_note, so an agent cannot tell from this text alone which creation path to pick.

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

Usage Guidelines2/5

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

The description lists kinds of notes but offers no when-to-use versus when-not guidance and never names an alternative. Nothing says whether to use this instead of save_note or write_project_update, or whether it should be avoided when a note already exists (update_note exists as a sibling). Usage is only implied by the examples.

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.

Resources