Skip to main content
Glama
alexrobl
by alexrobl

export_map_cartographic

Produce a formal cartographic map with institutional title, legend, scale bar, and credits. Includes a textual report of the symbology applied to each layer for verification.

Instructions

Genera un mapa cartográfico técnico con layout formal completo: título institucional · panel lateral (leyenda, convenciones, índice de localización) · franja inferior (norte, escala, parámetros/fuente). Devuelve además un reporte textual de la simbología realmente aplicada a cada capa: VERIFICARLO antes de afirmar que un color/estilo cambió.

Usar para productos formales ("mapa cartográfico", "carta", "entrega", "producto"). Para exploración rápida usar export_map_image.

Args: path: Ruta al archivo o directorio espacial. layer: Nombre de la capa (None = primera capa). limit: Máximo de features (default 5000). color_by: Campo para colorear por categoría (colores automáticos). where: Filtro SQL OGR. Si se aplica, la extensión del mapa se ajusta (zoom) a las features filtradas; las capas extra quedan como contexto recortado sin ampliar la vista. bbox: Extensión [xmin, ymin, xmax, ymax] en el CRS de la capa. style: Estilo avanzado (mismo formato que export_map_image): Categorizado: {"type":"categorized","field":"X", "categories":{"A":"#e74c3c"}} Graduado: {"type":"graduated","field":"X", "ramp":"RdYlGn_r","breaks":5} output_path: Ruta de salida. .jpg para trabajo, .pdf para entrega. Default: "{capa}_cartographic.jpg" junto al archivo fuente. dpi: Resolución (default 150). Con dpi > 150 los tiles del basemap se piden a mayor zoom para mantener la nitidez (descarga más tiles: más lento). figsize: [ancho, alto] en pulgadas. Default auto-calculado. title: Título del mapa. Default: nombre de la capa. credits: Texto de fuente/créditos para el panel inferior. Ej: "Fuente: IGAC 2024 | Sistema: WGS84 EPSG:4326" label_by: Campo para etiquetar features (colocación inteligente). extra_layers: Capas adicionales (mismo formato que export_map_image, incluida la clave 'crs' para capas sin CRS definido). IMPORTANTE: pasar SIEMPRE 'color' explícito y distinto por capa (matiz diferente) y 'label' descriptivo; el gris default es solo para capas de puro contexto. source_crs: CRS a asumir para la capa principal SOLO si el archivo no define uno (ej. "EPSG:3116"). Ver export_map_image. basemap: URL de un basemap alternativo al default CartoDB Positron: raíz de un ArcGIS MapServer con cache de tiles en Web Mercator o plantilla XYZ con tokens {z}/{x}/{y}. Ver export_map_image. markersize: Tamaño del marcador para capas de puntos, en pt². Default None = automático según número de puntos y ancho del lienzo, con halo blanco. Ver export_map_image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dpiNo
bboxNo
pathYes
layerNo
limitNo
styleNo
titleNo
whereNo
basemapNo
creditsNo
figsizeNo
color_byNo
label_byNo
markersizeNo
source_crsNo
output_pathNo
extra_layersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It discloses key behaviors: map layout components, return of a textual symbology report, DPI effect on basemap tile loading, extent adjustment with 'where' filter, and default marker size calculation. Lacks explicit safety (read-only) statement but otherwise thorough.

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?

The description is well-structured: overview, usage guidance, then detailed parameter list. It front-loads the essential purpose. However, it is lengthy and includes some redundancy (e.g., repeated 'Ver export_map_image'), making it slightly less concise.

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 17 parameters, no schema descriptions, and no annotations, the description covers all parameters and describes the output. It lacks explicit error handling or output format details, but overall is fairly complete for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description fully compensates by explaining each parameter in the 'Args' block, including purpose, defaults, examples, and important notes (e.g., 'extra_layers' requiring explicit colors). This adds significant meaning beyond the plain 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?

The description clearly states the tool generates a technical cartographic map with a formal layout, listing its components. It explicitly distinguishes itself from sibling tool 'export_map_image' by stating 'Para exploración rápida usar export_map_image', making the purpose and differentiation evident.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance: 'Usar para productos formales' and a direct alternative: 'Para exploración rápida usar export_map_image'. It also includes a behavioral warning to verify the textual report before claiming style changes.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alexrobl/geoanalisis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server