atlaspi-mcp

Overview Schema Source Related Servers Discussions Admin

get_evolution

Retrieve the timeline of territorial changes for a historical entity, including annexations, losses, capital changes, regime transitions, and unification or split events, with sources and acquisition methods.

Instructions

Restituisce la timeline dei cambi territoriali di una entita': annessioni, perdite di territorio, cambi di capitale, transizioni di regime, eventi di scissione o unificazione. Ogni evento ha anno, descrizione, fonte e (quando disponibile) acquisition_method per documentare se un territorio fu acquisito per conquista, matrimonio dinastico, trattato, ecc. Importante per ricostruire l'arco storico di un'entita' nel tempo.

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": {
      "entity_id": "<entity_id>"
    },
    "name": "get_evolution"
  }
}

Input Schema

Name	Required	Description	Default
`entity_id`	Yes	ID dell'entita' di cui ricostruire l'evoluzione.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.3Jul 24, 2026

TDQS

A3.7/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 full behavioral disclosure. It details output fields and event types, but does not mention ordering, pagination, data freshness, or whether all events are included. Some behavioral traits are left unspecified.

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 a single paragraph that front-loads the main purpose. It is reasonably concise and covers key aspects without unnecessary text.

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 the simple schema and no output schema, the description provides details about return fields and event types, which is valuable. It conveys the tool's purpose and output structure, making it mostly complete for an agent.

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 100% with entity_id described in the schema. The description adds no extra information about the parameter itself, only about the output. Baseline 3 is 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 clearly states the tool returns a timeline of territorial changes (verb+resource) and lists specific event types (annexations, losses, etc.) and output fields (year, description, source, acquisition_method). This distinguishes it from siblings like get_event or full_timeline_for_entity.

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

Usage Guidelines3/5

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

The description explains what the tool does and mentions it is important for reconstructing historical arcs, but does not explicitly state when to use it versus alternatives like entity_predecessors or full_timeline_for_entity. Usage context is implied but not definitive.

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