Skip to main content
Glama
Hackeatutiempo

Mapache

by Hackeatutiempo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Connect things

connect

Draw labeled arrows between nodes or items for flowcharts and relations; several per call, auto-routed and saved live.

Instructions

Draw connectors (arrows) between nodes and/or items, optionally with a label, for flowcharts and relations. Several in one call; each call adds new connectors (it does not replace existing ones). The path routes itself around other objects. 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 how many connectors were added. To change a connector later use update_items with its id.

Input Schema

NameRequiredDescriptionDefault
boardYesBoard id or title. Use "open" for the board the person has open in the app
connectionsYesOne entry per arrow

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.5.3
    • addedInput schema / properties / connections / description
      Added value: +"One entry per arrow"
    • addedInput schema / properties / connections / items / properties / from / description
      Added value: +"Start: a node or item id (from read_board or add_items), or its exact text"
    • addedInput schema / properties / connections / items / properties / label / description
      Added value: +"Text on the line, like \"Yes\" or \"No\""
    • addedInput schema / properties / connections / items / properties / route / description
      Added value: +"elbow (default): right angles, best for flowcharts. curved or straight for relations"
    • addedInput schema / properties / connections / items / properties / style / description
      Added value: +"Line style (default solid)"
    • addedInput schema / properties / connections / items / properties / to / description
      Added value: +"End, where the arrowhead goes: a node or item id, or its exact text"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: each call is additive ('does not replace existing ones'), paths auto-route around other objects, the change saves as a new revision and appears live, and it is undoable via Ctrl+Z. This is exactly the mutation/live-sync behavior an agent needs and the annotations don't supply.

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?

Front-loads what the tool does, then layers additivity, live-sync, return value, and the modify path in tight sentences with zero waste.

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?

With no output schema, the description still states the return ('how many connectors were added') and covers additivity, routing, persistence, and undo. Nothing an agent needs to call it correctly is missing.

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 100% with detailed nested descriptions for from/to/label/route/style/endCap, so the schema carries the semantics. The description only adds 'optionally with a label,' which the schema already documents, so baseline 3 applies.

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?

States a specific verb (Draw) and resource (connectors/arrows between nodes and items) plus the use case (flowcharts and relations). An agent can distinguish this from add_items and update_items without opening any schema.

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

Usage Guidelines4/5

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

Gives clear context (flowcharts and relations) and explicitly routes the modify case: 'To change a connector later use update_items with its id.' It stops short of stating when to add a connector vs. a node/item from add_items, so no full exclusion set.

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