Aeralas Maps

Preview a map (free, watermarked)

preview_map

Read-only

Render the map at screen size with a PREVIEW watermark and return it as an image, so the user can see the layout before buying. Same request as make_map. Free.

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.
`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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful behavior: watermarked output, screen-size rendering, image return, and free cost. It does not disclose rate limits or persistence details, but with annotations present the bar is lower.

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 with zero waste, front-loading the core action, output, watermark, use case, and free/paid distinction.

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 complex 15-parameter tool with no output schema, the description adequately covers what is returned (an image), the preview limitation (watermark), and how it relates to make_map. The remaining detail is carried by the rich schema and sibling relationship.

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 80%, so the schema already documents most parameters. The description adds no parameter-specific meaning beyond 'Same request as make_map,' making the baseline score of 3 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 states a specific verb and resource: render the map at screen size with a PREVIEW watermark and return it as an image. It also distinguishes the free preview from the paid sibling by saying 'Same request as make_map. Free.'

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 phrase 'so the user can see the layout before buying' gives a clear when-to-use context, and 'Same request as make_map. Free.' implies the preview precedes a paid make_map call. It does not explicitly name exclusions or route to check_map/revise_map, so it falls short of 5.

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?