Skip to main content
Glama
Sign In

Indicadores Argentina

by ar.indicadores
OverviewDiscussionsAdmin

Serie de migraciones

serie_migratoria
Read-only

Personas por origen y destino en una serie de migraciones de la Argentina, cada número con su fuente, página y cuadro, y si es observado o derivado. Lugares: país por slug (italia, bolivia, espana), 'ar' para la Argentina, 'ar-NN' para una provincia por código INDEC (ar-02 Ciudad de Buenos Aires, ar-06 Buenos Aires) y 'mundo' para el total. Ejemplos: argentinos en España según la ONU (serie stock_migrantes_onu, origen argentina, destino espana); italianos en Santa Fe por censo (nacidos_en_el_extranjero, origen italia, destino ar-82). Gratis.

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": {
      "serie": "<serie>"
    },
    "name": "serie_migratoria"
  }
}

Input Schema

NameRequiredDescriptionDefault
sexoNot total (default), v varones, m mujeres, x sexo X
desdeNoprimer año AAAA
hastaNoúltimo año AAAA
serieYesserie a consultar (ver migraciones_disponibles)
origenNolugar de origen: país por slug, ar, ar-NN o mundo
destinoNolugar de destino: país por slug, ar, ar-NN o mundo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, non-open-world behavior. The description adds useful context such as 'Gratis' and that each number carries its source, page, table, and observed/derived status.

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?

Front-loads the purpose, then compactly explains location slugs and gives examples with no wasted sentences. Every part contributes to correct invocation.

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?

No output schema exists, so the description helpfully explains that returned numbers include source, page, table, and observed/derived status. It does not describe the full response shape or pagination, but is adequate for a data-series query tool.

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%, so baseline is 3. The description adds concrete slug examples ('italia', 'bolivia', 'espana'), INDEC province codes ('ar-02 Ciudad de Buenos Aires', 'ar-82 Santa Fe'), and a worked serie+origen+destino example, going beyond the schema's brief parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specifically that it returns people by origin and destination from an Argentine migration series, including source/page/table metadata. Clear resource and scope, but does not explicitly distinguish itself from the sibling migraciones_disponibles tool.

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 concrete usage examples that show how serie, origen, and destino combine, e.g. argentinos en España según la ONU. It gives clear context but does not explicitly say when to prefer this tool over migraciones_disponibles or other siblings.

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

All Indicadores Argentina toolsInspect
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