mappls-mcp

still_map_image

Generate a static map image URL centered on a location. Returns a PNG map image for embedding in reports or sharing via email or messaging.

Instructions

Generate a static map image URL centered on a location. Returns a URL to a PNG map image — useful for embedding maps in reports or sending via WhatsApp/email.

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": {
      "lat": "<lat>",
      "lng": "<lng>"
    },
    "name": "still_map_image"
  }
}

Input Schema

Name	Required	Description
`lat`	Yes	Center latitude
`lng`	Yes	Center longitude
`zoom`	No	Zoom level 4–18 (default 15)
`width`	No	Image width in pixels (default 800)
`height`	No	Image height in pixels (default 600)
`markers`	No	Optional marker as 'lat,lng' to pin on the map

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Jul 28, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states that the tool returns a URL to a PNG image, which is clear, but it does not disclose potential side effects (none expected for a read operation), authentication requirements, or error cases. The behavioral traits are implied but not explicitly detailed.

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?

The description is only two sentences. The first sentence immediately states the core function, and the second provides practical use cases. There is no extraneous information, making it highly efficient.

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?

Given the tool's moderate complexity (6 parameters, all self-documented) and the absence of an output schema, the description sufficiently covers what the tool does and typical usage. It could be slightly improved by mentioning that the URL is generated server-side, but overall it is complete enough.

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?

The input schema has 100% description coverage, so each parameter is already documented. The description adds no additional meaning beyond 'centered on a location.' With high schema coverage, a baseline score of 3 is appropriate.

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?

The description uses the specific verb 'Generate' and names the resource 'static map image URL'. It clearly distinguishes from sibling tools like geocode or get_directions, as it focuses on creating an image URL rather than performing spatial lookups or route calculations.

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?

The description gives explicit use cases: 'embedding maps in reports or sending via WhatsApp/email.' This provides clear context for when the tool is appropriate, though it lacks explicit guidance on when not to use it or alternatives.

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

Deploy Server