Skip to main content
Glama

Banquish

Add a Note

add_note

Add a Note to a Workspace: a few words of your own beside its Panels. Formatted text only, shown in Banquish's own style: "# Heading" (or "## Smaller heading"), paragraphs, "- " or "1. " list items, and links; anything else, HTML included, shows as the text it is. No bold or italic: write plain words (** is dropped). At most 2000 characters. Placement is where its Tile goes on the grid, as in arrange; without one it goes full width below the last Tile. With h, a Note's Tile is that tall, even taller than its text. The user can undo it with the rest of your Working stretch. Returns the Fit report: at the user's window, which Tiles are scaled below their Panel's minimum width, scroll inside, fell back to crop, are broken or ambiguous, or leave their Tile's width unused, and any gaps between Tiles; and, not as an issue, which Panels are shorter than the h of their Tile, so show centred in it. A Tile whose page hasn't laid it out at its width yet (one not on screen, say) is settling: a later report says how it fits. While a settling Tile's minimum width isn't known, whether the Workspace shows as one column isn't either: oneColumn is left out, and the summary says so.

Input Schema

NameRequiredDescriptionDefault
textYes
placementNo
workspaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds substantial context on top: a 2000-character cap, undo scope tied to the Working stretch, exact default placement, and the meaning of h overriding text height. It also discloses a non-obvious edge case — a settling Tile leaves oneColumn out of the report.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Everything is front-loaded correctly, but it arrives as one dense run-on block with heavy jargon (Banquish, Tile, Panel, Working stretch, Fit report) and the lengthy Fit-report catalogue occupies half the text. Each clause carries information, yet the lack of structure makes it hard to scan.

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?

No output schema exists, so the description correctly takes on the return value, enumerating the Fit report's issue categories and the settling-Tile caveat. It is close to complete for a mutation tool with a nested placement object; only the workspace identifier format and error behavior are unaddressed.

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?

With 0% schema description coverage, the description carries the load and does well: text is constrained to formatted-text syntax with a length limit, and placement is explained as grid coordinates analogous to arrange, including the h-vs-text-height rule. The workspace parameter's expected form (id vs. name) is left unexplained, and x/w/y are only covered indirectly by reference to arrange.

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?

The opening states a specific verb and resource — "Add a Note to a Workspace" — and clarifies the note sits "beside its Panels," which makes the artifact concrete. It never explicitly separates itself from update_note or remove_note, but the create semantics are unambiguous.

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?

Usage is implied by "Add a Note to a Workspace" and the reference to arrange for placement, but there is no statement of when to add a note versus a panel, no prerequisites, and no pointer to update_note for edits. The agent must infer the routing.

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.