Skip to main content
Glama
DChuhin
by DChuhin

create_sticky_note

Adds a sticky note to a Miro board at a chosen position, letting you capture ideas, tasks, labels, or annotations with a semantic color.

Instructions

Creates a sticky note on a Miro board at a specified position. Use this to add ideas, tasks, labels, or annotations. You can optionally place it inside a frame. Choose a color that matches the semantic meaning (e.g. yellow for ideas, red for blockers, green for done).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX coordinate (board center is 0)
yYesY coordinate (board center is 0)
colorYesFill color: yellow, light_yellow, orange, light_green, green, dark_green, cyan, light_pink, pink, violet, red, light_blue, blue, dark_blue, gray, black, white
widthNoSticky width in pixels (default 200)
contentYesText content of the sticky note
board_idYesMiro board ID
frame_idNoIf provided, places the sticky inside this frame

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It discloses useful behavior (optional frame nesting, color semantics), but says nothing about permissions/authorization, what happens on invalid frame_id, or the returned result for this mutation. Adequate but incomplete for a write operation with zero annotation coverage.

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 tight sentences, front-loaded with the core operation, then usage, then optional behavior and color guidance. No filler; each sentence earns its place.

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 no output schema and no annotations, the description covers purpose, usage, frame placement, and color semantics well. It is slightly thin on authorization/prerequisites and return behavior for a create tool, but nothing critical for correct invocation is missing.

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?

Schema coverage is 100% so the baseline is 3, and the description goes beyond the schema by explaining the semantic intent of the color parameter (yellow=ideas, red=blockers, green=done) and the frame_id nesting behavior, adding meaning the enum alone does not convey.

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?

Specific verb (creates) plus resource (sticky note) plus scope (Miro board, specified position), and it implicitly distinguishes itself from siblings like create_shape and create_connector by naming the concrete artifact. An agent can route to it without opening the schema.

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?

The description gives concrete intended uses ('add ideas, tasks, labels, or annotations') and mentions optional frame placement, but never states when NOT to use it or names the alternative tools (e.g. create_shape for non-sticky content). Usage is implied rather than contrasted with siblings.

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