Skip to main content
Glama
Sign In
atlaspi-mcp

atlaspi-mcp

by Soil911
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

snapshot_at_year

Retrieve all geopolitical entities active in a specified year, filtered by type or continent. Use this to answer historical political geography queries.

Instructions

Restituisce uno snapshot del mondo in un dato anno: tutte le entita' geopolitiche attive in quell'anno (year_start <= anno <= year_end), con possibilita' di filtrare per tipo o continente. Usa questo tool per domande del tipo 'che mappa politica c'era nel 300 a.C.?' o 'quali regni esistevano in Africa nel 1500?'. Ricorda: gli anni negativi sono a.C.

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": {
      "year": "<year>"
    },
    "name": "snapshot_at_year"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoTipo di entita' geopolitica. Esempi: empire, kingdom, republic, city-state, sultanate, caliphate, khanate, dynasty, principality, confederation, federation, duchy, colony, disputed_territory, city.
yearYesAnno (intero). Anni negativi rappresentano date a.C. Esempi: -300 = 300 a.C., 476 = 476 d.C.
continentNoContinente o macro-regione. Valori comuni: Europe, Asia, Africa, Americas, Middle East, Oceania.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.3

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 must carry the behavioral burden. It explains the year range logic and negative years for BC, but lacks details on result limits, ordering, or potential performance constraints.

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?

Two sentences plus a reminder are efficient and front-loaded with purpose. However, the reminder could be integrated or made more natural.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a filtered-listing tool with 3 parameters and no output schema. Provides core functionality but omits details like pagination, result format, or error cases.

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 value by explaining that entities are filtered by year_start≤year≤year_end and giving examples for type parameter. It mentions continent macro-regions, though not a complete list.

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 returns a world snapshot for a given year, listing all geopolitical entities active that year, with optional type and continent filters. This distinguishes it from sibling tools like get_route or where_was.

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?

Provides explicit usage examples (e.g., 'che mappa politica c'era nel 300 a.C.?') and clarifies when to use. However, it does not mention when not to use or suggest alternatives.

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

Deploy Server

Other Tools