Skip to main content
Glama

add_mountain_range

Place mountain symbols along a polyline as a land-only ribbon, using pixel width and density per 100x100 px area to control range coverage.

Instructions

Place mountains in a ribbon of the given width (px) along a polyline (land only). density is symbols per 100x100 px of ribbon area.

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": {
      "set_key": "<set_key>",
      "polyline": "<polyline>",
      "width": "<width>",
      "density": "<density>"
    },
    "name": "add_mountain_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoRandom seed (0 to 2^32-1); the same seed gives the same result.
widthYes
densityYes
set_keyYes
polylineYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden and does not say whether the call mutates the map, whether it is undoable, whether it requires an open map or an active layer, or what it returns. The only behavioral fact given is the land-only restriction, which is genuinely useful but thin for a mutation tool with zero annotation coverage.

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?

Two tightly packed sentences that front-load the action and the geometric constraint before the density formula. No filler, though the parenthetical unit and density sentence run together in a way that reads slightly like notes than guidance.

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?

For a five-parameter placement tool with no output schema and no annotations, the description conveys the core spatial model and the meaning of the two quantitative parameters. It falls short on set_key, polyline coordinate format, and mutation/undo semantics, which an agent still needs in order to invoke it confidently.

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 description coverage is only 20% (seed alone), so the description must compensate, and it does for two of the four required parameters: width is defined as pixels and density as symbols per 100x100 px of ribbon area. set_key and polyline remain completely unexplained in both schema and description, and the width unit is only implied by '(px)'.

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 description names a specific verb and resource ('Place mountains') and constrains it to a geometric footprint ('ribbon of the given width ... along a polyline'), which is enough to distinguish it from siblings like add_forest or add_lake. It does not explicitly say how it differs from those siblings, so it stops short of a 5.

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?

The parenthetical 'land only' is a real usage constraint that tells the agent to avoid water areas. Beyond that there is no when-to-use guidance, no prerequisites (e.g. must a map be open first), and no mention of alternatives for placing terrain symbols.

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