Tuper maps

Get a free SVG map

get_free_map

Read-only

Returns the SVG source of one free map (blank world, blank US states, blank US counties, blank maps of countries and continents, labelled Switzerland cantons) with its region names. Every region is one with id and data-name, ready to recolour as a choropleth. Free for any use. Pass id from list_maps or find_map (e.g. "free-blank-japan-map-svg"), or a place name ("Japan").

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": {
      "id": "<id>"
    },
    "name": "get_free_map"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Map id or place name
`force`	No	return the SVG even when it is larger than 400 KB (US counties is about 1 MB)
`include_svg`	No	false = only metadata, region names and download URL

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, and the description adds real context beyond that: the SVG is structured as one <path> per region with id and data-name, and licensing is stated ('Free for any use'). It omits the practical 400 KB size ceiling, though the schema's `force` parameter already surfaces that.

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?

Four sentences, roughly 80 words, front-loaded with the return payload before the routing hint. Every sentence contributes: scope, structure, licensing, invocation.

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?

There is no output schema, and the description carries that burden fully by describing both the payload (SVG source plus region names) and its internal structure. Nothing an agent needs to call this correctly is missing.

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 the baseline is 3; the description still adds value by giving a concrete id format example ('free-blank-japan-map-svg') and confirming place names work. It says nothing extra about `force` or `include_svg`, but the schema handles those adequately.

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?

Names a specific verb and resource ('Returns the SVG source of one free map') and enumerates exactly which map families are covered, so scope is unambiguous. The agent can tell it apart from find_map/list_maps 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 Guidelines4/5

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

Gives explicit routing: 'Pass id from list_maps or find_map', establishing the discovery-then-fetch workflow, and notes a place name is also acceptable. No explicit when-not-to-use case, but the sibling roles are clear enough that little is left to inference.

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

All Tuper maps tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?