Skip to main content
Glama

add_path

Draw roads or paths through specified points on a Wonderdraft map; out-of-bounds points are clamped to the map edge, with configurable style, width, color, roughness, and seed.

Instructions

Add a road/path along points; points outside the map are clamped to its edge (clamped = how many). style is one of Wonderdraft's path textures: path_blended, path_circle, path_dash, path_dash_dot, path_dash_dot_dot, path_directional, path_double_paired, path_hash_marks, path_solid, path_solid_outlined. width in px; roughness is the wobble (0 = smooth, ~0.3 default).

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": {
      "points": "<points>"
    },
    "name": "add_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoRandom seed (0 to 2^32-1); the same seed gives the same result.
colorNo
styleNopath_blended
widthNo
pointsYes
roughnessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose one genuinely non-obvious behavior: out-of-bounds points are clamped to the map edge. However, it omits other traits an agent needs for a mutation tool: whether the created object is undoable, what identifier is returned, and any permission or open-map requirement. The garbled '(clamped = how many)' further muddies the clamp disclosure.

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

Conciseness4/5

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

The purpose is front-loaded and every subsequent clause adds parameter meaning rather than filler. The parenthetical '(clamped = how many)' is an awkward, half-finished phrase that costs clarity, but overall density is good.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter creation tool with no annotations and no output schema, the definition covers the style vocabulary and roughness scale well but leaves the required points structure, color format, and return value unexplained. The clamp note hints at a return count without committing to a response shape.

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 only 17%, so the description has to compensate, and it does for three parameters: it enumerates all ten valid style textures (the schema has no enum), gives width units in px, and explains roughness as wobble with smooth=0 and default ~0.3. It adds nothing for the required 'points' parameter's coordinate format or for 'color', leaving real gaps.

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 first clause names a specific verb and resource ('Add a road/path along points'), which is clearly distinct from siblings like add_river, add_forest or add_symbol. It stops short of explicitly contrasting itself with those drawing tools, but an agent can identify the operation 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 Guidelines2/5

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

There is no when-to-use guidance: no mention of a prerequisite open map, no statement of when to draw a path versus a river or territory outline, and no notes on ordering or interaction with update_object/undo. Usage is only inferable from the verb.

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