Skip to main content
Glama

Add a map from a picture's link

add_map

Add a map to the campaign from a picture's web address (PNG, JPEG, WebP or GIF, up to 60 MB, reachable without signing in). The address is checked now; the map is cut into zoomable tiles the next time the GM opens the Map tab in the app, and shows up for the table once that is done. Until then it is listed to the GM as pending, and pins wait for it to be ready. GM only. Returns: The map's id (what pins are placed against) and status: "pending".

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": {
      "campaign": "<campaign>",
      "name": "<name>",
      "imageUrl": "<imageUrl>"
    },
    "name": "add_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesWhat the map is called on its tab.
campaignYesThe campaign, by its slug (what its link says) or its id.
imageUrlYesThe picture's full web address, starting https://.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare non-read-only, open-world, non-idempotent and non-destructive, so the mutation profile is covered. The description still adds real value beyond them: the URL is validated synchronously, tiling is deferred until the GM opens the Map tab, the map shows as pending, and pins block on readiness, plus a GM-only auth requirement.

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?

Front-loads purpose, then explains the deferred-tiling lifecycle, then the return value — a logical order with no filler. The parenthetical format/size/reachability clause is dense but each element is operationally relevant.

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?

No output schema exists, yet the description names the return payload (map id and status 'pending'). Combined with the async readiness explanation and the GM constraint, an agent has everything needed to call it and to set user expectations afterwards.

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?

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond it: imageUrl accepts PNG/JPEG/WebP/GIF up to 60 MB and must be publicly reachable, and campaign is referenced by slug or id. Only `name` semantics are left entirely to the schema.

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 and resource with its source: 'Add a map to the campaign from a picture's web address.' This cleanly separates it from update_map (existing maps), create_pin (pins on a map), and add_character_from_beyond (other upload paths) without needing to open a 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 operative context: it must be a URL reachable without signing in, and the caller must be a GM. It does not explicitly route to alternatives (e.g., update_map for an existing map, or how to replace a bad image), so the when-not side is left implicit.

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.