Skip to main content
Glama
Hackeatutiempo

Mapache

by Hackeatutiempo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Add notes, shapes, tables…

add_items

Insert notes, text, shapes, sections, stickers, tables, charts, or video embeds into a board; saves as a new revision and appears live in open browsers.

Instructions

Add sticky notes, text, shapes, sections, stickers, tables, charts or video embeds to a board. They are laid out together in free space unless each has x and y. To chart data, add a table first, then a chart with its id. It is saved at once as a new revision of the board and appears live in any browser that has it open (the person can undo it with Ctrl+Z). Returns each new item with its type and id (use the ids with connect, update_items or a chart's table). For mind map branches use add_nodes instead.

Input Schema

NameRequiredDescriptionDefault
xNoTop-left of the group. Usually leave it out: Mapache places the group in free space
yNoSee x
boardYesBoard id or title. Use "open" for the board the person has open in the app
itemsYesThe items to add, placed as a group

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.5.3
    • addedInput schema / properties / items / description
      Added value: +"The items to add, placed as a group"
    • addedInput schema / properties / items / items / properties / h / description
      Added value: +"Height in board units (default depends on the type)"
    • addedInput schema / properties / items / items / properties / type / description
      Added value: +"What to add: a sticky note, free text, a shape (for flowcharts), a named section that groups things, an emoji sticker, a table, a chart of a table, or a video embed"
    • addedInput schema / properties / items / items / properties / w / description
      Added value: +"Width in board units (default depends on the type; notes and shapes also grow with their text)"
    • addedInput schema / properties / items / items / properties / y / description
      Added value: +"Top of the item, in board units (see x)"
    • addedInput schema / properties / y / description
      Added value: +"See x"
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare only write/idempotency flags, but the description adds genuinely new behavioral context: the change is committed immediately as a new board revision, syncs live to open browsers, is reversible by the human via Ctrl+Z, and auto-places items in free space unless x/y are given. Because there is no output schema, it also discloses the return value (each new item with its type and id).

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?

Four sentences, front-loaded with the core action and item types, then sequencing, then side effects, then the sibling redirect. Every sentence carries a distinct piece of information with no restatement of the schema.

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 non-idempotent mutation tool with no output schema, the description covers what is created, how it is placed, the table-before-chart dependency, the immediate revision/live-sync/undo behavior, and the return shape. Nothing an agent needs to call or chain this tool 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, but the description adds semantics the schema does not: items are grouped and laid out in free space unless x and y are supplied, and a chart's table parameter must reference a previously added table's id. That sequencing and layout rule is real added value beyond the per-field descriptions.

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?

Opens with a specific verb and resource ("Add sticky notes, text, shapes, sections, stickers, tables, charts or video embeds to a board") and enumerates the item types, so the agent knows exactly what it produces. It also names the sibling it is not ("For mind map branches use add_nodes instead"), making it distinguishable 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?

Gives explicit routing guidance: use add_nodes for mind map branches, and for charts add a table first then reference it by id. It also points forward to downstream tools (connect, update_items) for the returned ids, leaving little to inference.

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