Skip to main content
Glama

Unhcr

by io.github.pipeworx-io
OverviewAdmin

Asylum Applications

asylum_applications
Read-onlyIdempotent

Asylum applications lodged, by year, country of origin (coo) and country of asylum (coa). Rows carry procedure_type, app_type, dec_level and the applied count; response.total.applied is the aggregate. 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": 2021,
+    "yearTo": 2023
+  },
+  {
+    "coa": "PAK",
+    "coo": "AFG",
+    "yearFrom": 2022,
+    "yearTo": 2023
+  }
+]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint true and destructiveHint false, so the description does not need to repeat safety traits. The description adds minor context about response structure (e.g., response.total.applied is aggregate) but no significant behavioral disclosure beyond 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?

Two sentences efficiently convey the purpose, grouping, row structure, and aggregate. Every sentence earns its place with no fluff.

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?

The description covers the core data and row structure, but does not mention pagination defaults (e.g., page, limit from schema) or explain the year range behavior. However, with good annotations and 100% schema coverage, it is largely adequate for a list 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 description coverage is 100%, but the description adds value by explaining that coo/coa use UNHCR 3-letter codes (referencing list_countries) and describing the row fields (procedure_type, app_type, dec_level, applied count) and aggregate, which are not detailed in the schema.

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 'Asylum applications lodged, by year, country of origin (coo) and country of asylum (coa)', which specifies the verb (retrieve/query), the resource (asylum application counts), and the grouping dimensions. This contrasts with sibling 'asylum_decisions', making the tool's purpose distinct.

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

Usage Guidelines2/5

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

No explicit guidance is provided on when to use this tool versus alternatives like asylum_decisions. The only reference is 'see list_countries' for codes, which is about input format, not usage context.

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