Skip to main content
Glama

create_serbia_map

Generate a color-coded choropleth map of Serbia's 25 administrative districts from tabular data. Specify district names, values, and customize title, theme, and color scale.

Instructions

Choropleth map of Serbia by 25 administrative districts. Color-coded by metric.

District names in Natural Earth format (English transliteration). Cyrillic and city shorthand also supported (e.g., 'Niš', 'Novi Sad'). Use list_serbia_districts() to see all recognized names.

Returns: {filepath, districts_matched, total_districts, title}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesRow dicts with district names and values
themeNo'dark', 'light', 'infographic'dark
titleNoMap title
filenameNoOutput filename (without .html)serbia_map
colorscaleNo'red', 'blue', 'diverging', 'heat' (default: blue)
name_columnYesDistrict names column
value_columnYesNumeric values to color by

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description fully discloses the mapping behavior, supported name formats, and return values, but could mention any side effects or limitations.

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 brief yet comprehensive, with no redundant sentences, and efficiently uses three paragraphs for key information.

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?

For a 7-parameter mapping tool with an output schema, the description covers input, output, and special constraints (name formats), making it fully informative.

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%, but the description adds practical context about district name formats and the helper tool, enhancing parameter understanding beyond the 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 it creates a choropleth map of Serbia by 25 administrative districts, which is specific and distinguishes from sibling tools like bubble maps or multi-layer maps.

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 implies usage for Serbian district maps and provides a helper tool reference, but lacks explicit when-not or alternative tool guidance.

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/acailic/serbian-data-mcp'

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