Skip to main content
Glama

add_text

Add text at board coordinates. Requires an edit link; changes appear live.

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
textYes
colorNo#1f2937
boardUrlYesA JotPond /b/<edit-id> or /view/<read-only-id> link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish that this is a non-destructive write. The description adds two useful behaviors beyond them: the operation needs an edit-capable link (not a read-only /view/ link) and the result publishes live rather than being staged. It says nothing about reversibility, whether the text can later be deleted, or what identifiers come back.

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?

Two short sentences with the action and the hard prerequisite front-loaded, zero filler. Nothing redundant or padded.

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 5-parameter mutation with low schema coverage and no output schema, the description is thin: the undocumented color parameter, the missing return-value context (does it return an item id usable with delete_item?), and no linkage to delete_item for correction.

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 only 20% (boardUrl is the sole documented property), so the description must compensate and does not. It alludes to coordinates and the link but says nothing about the color parameter or the text length constraints; a caller must read the schema to learn the color format.

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?

"Add text at board coordinates" states a specific verb plus resource and scopes the effect to the board surface, which separates it from read_board or clear_board. It never names add_stroke, so the closest sibling distinction (text vs. stroke) is left implicit.

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?

"Requires an edit link" gives a real precondition that rules out tools/links the agent might otherwise try, but there is no statement of when to prefer this over add_stroke or when not to use it at all.

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.

Resources