Skip to main content
Glama
Sign In
Easel

Easel

by nemodleo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_note

Add a large title heading or sticky note to the canvas at chosen coordinates to annotate designs and organize content.

Instructions

Add a note to the canvas. kind=title (large heading) or sticky (sticky note).

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": {
      "kind": "<kind>",
      "text": "<text>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "add_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
wNo
xYes
yYes
kindYes
pageNo
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden but discloses almost no behavior beyond the fact that a note is created. It does not say whether the note appears immediately, what permissions are required, whether coordinates are absolute or viewport-relative, or what happens when page/w are omitted.

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 short sentences, front-loaded with the action and followed by the kind semantics. Every sentence earns its place, though the extreme terseness leaves important gaps rather than being maximally useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter mutation tool with no annotations and no output schema, the description is markedly incomplete. It says nothing about coordinate semantics, the page parameter, the width parameter, or the result of the operation, so an agent cannot confidently invoke it without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, but it only explains the kind parameter's two enum values. The required text, x, and y parameters and the optional page and w parameters are left completely undocumented.

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 ('Add a note to the canvas') and explains the two note kinds with their visual meaning. It does not explicitly distinguish itself from siblings such as add_comment or update_note, but the action is clear.

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?

There is no guidance on when to use add_note versus update_note, add_comment, or place_board, nor any prerequisites. The only usage hint is the kind distinction, which is implicit at best.

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

Deploy Server

Other Tools