Skip to main content
Glama

Buscar indicadores sociales del MIDES

buscar_indicador_social
Read-onlyIdempotent

Search Uruguay's MIDES social indicators by keyword to find indicator names for use with indicador_social. Include 'departamento' for department-level results.

Instructions

Busca entre los ~1.260 indicadores sociales del Observatorio Social del MIDES (pobreza, empleo, desempleo, educación, vivienda, salud, ingresos, cuidados, juventud, personas mayores, censos...) por palabras, sin tildes. Devuelve los nombres para pasar a indicador_social. Para un departamento, incluir la palabra 'departamento' (por ejemplo 'pobreza departamento').

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": {
      "texto": "<texto>"
    },
    "name": "buscar_indicador_social"
  }
}

Input Schema

NameRequiredDescriptionDefault
textoYes
cantidadNo

Output Schema

NameRequiredDescriptionDefault
notaYes
avisoNo
totalYes
bajadoYes
fuenteYes
encontradosYes
indicadoresYes
copia_vencidaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.14.0
    • addedOutput schema / properties / aviso
      Added value: +{
      +  "title": "Aviso",
      +  "type": "string"
      +}
    • addedOutput schema / properties / copia_vencida
      Added value: +{
      +  "title": "Copia Vencida",
      +  "type": "boolean"
      +}
  2. First observedv0.13.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description's added value is what it discloses about behavior: the corpus size (~1,260 indicators), accent-insensitive matching ('sin tildes'), and that it returns only names rather than values. It does not discuss zero-result behavior or how results are ranked/truncated, which keeps it from a 5.

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?

Three tight sentences, front-loaded with the corpus and search modality, followed by the downstream routing and the department tip. The long parenthetical topic list is slightly heavy but earns its place by telling the agent what vocabulary to search with.

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?

With an output schema present, the description need not detail return values, and it still notes that names are returned. Annotations handle the safety profile. The remaining gap is the undocumented 'cantidad' cap, which matters for an agent deciding how many candidates to pull.

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 description coverage is 0%, so the description carries the burden and does explain 'texto' well: free words, no accents needed, and the 'departamento' keyword convention. However, the second parameter 'cantidad' (default 20) is never mentioned, so only half the inputs get semantic treatment.

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?

States a specific verb (busca) and resource (the ~1,260 indicadores sociales of the MIDES Observatorio Social), enumerates the topical scope, and explicitly positions itself as a precursor to the sibling indicador_social. An agent can distinguish it from indicador_social without opening either schema.

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?

Gives the workflow explicitly: search here, then pass the returned names to indicador_social. It also supplies a concrete query-construction rule (include the word 'departamento' to get departmental-level indicators). It stops short of stating when this tool should NOT be used, but the routing intent is clear.

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