Skip to main content
Glama

Unhcr

by io.github.pipeworx-io
OverviewAdmin

Asylum Decisions

asylum_decisions
Read-onlyIdempotent

Decisions on asylum claims, by year, country of origin (coo) and country of asylum (coa). Each row breaks out dec_recognized, dec_other, dec_rejected, dec_closed and dec_total; response.total aggregates the same fields. coo/coa take UNHCR 3-letter codes (see list_countries).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coaNoCountry of ASYLUM — UNHCR 3-letter code.
cooNoCountry of ORIGIN — UNHCR 3-letter code.
pageNo1-based page.
limitNoRows per page (default 25).
yearToNoEnd year, inclusive.
yearFromNoStart year, inclusive.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "yearFrom": 2020,
+    "yearTo": 2023
+  },
+  {
+    "coa": "DEU",
+    "yearFrom": 2022,
+    "yearTo": 2023
+  }
+]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already indicate readOnly, openWorld, idempotent, non-destructive. The description adds behavioral details: row fields (dec_recognized, etc.) and that response.total aggregates the same fields. No contradiction with annotations.

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?

Three sentences, front-loaded with purpose, each sentence adds necessary detail without waste. Examples in schema supplement but description itself is concise.

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 good annotations and full schema coverage, the description is complete for a data retrieval tool. It explains row fields and aggregation, though no output schema is present.

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 covers 100% of parameters with descriptions. The description adds value by explaining that coo/coa take UNHCR 3-letter codes and referencing list_countries, providing context beyond schema.

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?

The description clearly states it returns 'Decisions on asylum claims, by year, country of origin (coo) and country of asylum (coa)' and specifies the breakdown fields (dec_recognized, etc.). It differentiates from siblings like asylum_applications by focusing on decisions, though not explicitly contrasting.

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?

No explicit when-to-use or when-not-to-use guidance. It implies usage for retrieving asylum decision data and references list_countries for codes, but lacks alternatives or exclusions.

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

All Unhcr toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources