Aeralas Maps

Buy a print-ready map

make_map

Render the print-resolution map and return a download link. Costs $1 USDC, paid over x402: the first call returns the payment requirements; sign and call again with the payment. Charged only if the render succeeds. Includes 7 days of free revisions via revise_map.

Input Schema

Name	Required	Description	Default
`dpi`	No
`mapId`	No	Revise a map you already bought. Returned as X-Map-Id on your paid export. Re-exports are free for 7 days as long as the FRAME is unchanged — change labels, styling, overlays and page elements freely; changing address, center, groundWidthM, pageSize, orientation or dpi makes it a different map.
`title`	No	Title block heading. Defaults to the address.
`center`	No	[longitude, latitude] in WGS84. Alternative to address.
`format`	No		pdf
`address`	No	US street address, city and state. Geocoded via the US Census.
`overlays`	No	Thematic layers drawn under the annotations. A legend is added automatically. fema-flood: regulated floodplain (blank means no mapped hazard — FEMA draws Zone X with no symbol). nwi-wetlands: USFWS National Wetlands Inventory.
`pageSize`	No		tabloid
`autoLabel`	No	Draft tenant callouts from OpenStreetMap and road names from Census TIGER before drawing your own. Use this when you do not know what is at the location. Pass an object to control how many: fewer labels is the simplest cure for a crowded page.
`labelScale`	No	Text size multiplier applied to every annotation that does not set its own textScale. Drop to ~0.8 to fit more labels; raise for a map read at arm’s length.
`annotations`	No	Callouts to draw. Placement, collision avoidance and leader lines are automatic.
`orientation`	No		portrait
`groundWidthM`	No	True ground width of the frame in meters. 500 fits a typical retail plaza; 20000-40000 makes a regional map, where autoLabel drafts cities, highway shields and water instead of tenants.
`pageElements`	No	Page furniture. Turn elements off to free up room for labels.
`imagerySourceId`	No	Imagery source id. Defaults to the sharpest source covering the frame.
`titleBlockScale`	No	Size multiplier for the title block.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 29, 2026
- changedInput schema / properties / annotations / items / properties / boxColor / maxLength
```
Previous value: -32New value: +40
```
- addedInput schema / properties / annotations / items / properties / boxColor / pattern
```
Added value: +"^(#[0-9a-f]{3,8}|[a-z]{3,20}|rgba?\$\\s*[\\d.]+%?\\s*(,\\s*[\\d.]+%?\\s*){2,3}\$)$"
```
- changedInput schema / properties / annotations / items / properties / color / maxLength
```
Previous value: -32New value: +40
```
- addedInput schema / properties / annotations / items / properties / color / pattern
```
Added value: +"^(#[0-9a-f]{3,8}|[a-z]{3,20}|rgba?\$\\s*[\\d.]+%?\\s*(,\\s*[\\d.]+%?\\s*){2,3}\$)$"
```
- changedInput schema / properties / annotations / items / properties / inkColor / maxLength
```
Previous value: -32New value: +40
```
- addedInput schema / properties / annotations / items / properties / inkColor / pattern
```
Added value: +"^(#[0-9a-f]{3,8}|[a-z]{3,20}|rgba?\$\\s*[\\d.]+%?\\s*(,\\s*[\\d.]+%?\\s*){2,3}\$)$"
```
- changedInput schema / properties / annotations / items / properties / markColor / maxLength
```
Previous value: -32New value: +40
```
- addedInput schema / properties / annotations / items / properties / markColor / pattern
```
Added value: +"^(#[0-9a-f]{3,8}|[a-z]{3,20}|rgba?\$\\s*[\\d.]+%?\\s*(,\\s*[\\d.]+%?\\s*){2,3}\$)$"
```
- changedInput schema / properties / annotations / items / properties / outlineColor / maxLength
```
Previous value: -32New value: +40
```
- addedInput schema / properties / annotations / items / properties / outlineColor / pattern
```
Added value: +"^(#[0-9a-f]{3,8}|[a-z]{3,20}|rgba?\$\\s*[\\d.]+%?\\s*(,\\s*[\\d.]+%?\\s*){2,3}\$)$"
```
First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only say it is not read-only, is open-world and non-idempotent. The description goes well beyond that by disclosing the $1 USDC price, the exact two-step payment handshake (requirements returned on first call, then sign and re-call), and success-only billing — critical facts no structured field carries.

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?

Three short sentences, each earning its place: what it returns, what it costs and how payment works, and where revisions belong. Front-loaded with the outcome and download link.

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?

Covers the highest-stakes unknowns for a paid, 16-parameter render tool: price, payment flow, billing on failure, and the free-revision escape hatch. It omits two useful details an agent would otherwise infer from the schema only — that X-Map-Id comes back on a paid export, and that address or center must supply the frame.

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 75% and the nested annotation object is documented in detail, so the schema is doing the heavy lifting. The description adds nothing about any of the 16 parameters, not even the dpi/pageSize tradeoffs implied by 'print-resolution'. Baseline 3 applies.

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 ('Render the print-resolution map and return a download link') and implicitly separates itself from preview_map by the word 'print-resolution'. It also names revise_map as the follow-on path, so an agent can place it among its siblings without opening any 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 strong operational context: the x402 two-call payment flow, that the charge only lands on a successful render, and that revisions go through revise_map. It stops short of an explicit 'call preview_map first to iterate for free' exclusion, which is the most likely routing question an agent will have.

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

All Aeralas 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?