Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_numbeo_countries_search

Search and filter country-level data from Numbeo's composite indices, including cost of living, quality of life, safety, crime, health care, pollution, and traffic. Supports sorting and pagination.

Instructions

Search the Numbeo countries dataset. Searches the composite Numbeo countries dataset, merged from the current global by-country rankings of all seven index families. Sort enum: name_asc, cost_of_living_asc, cost_of_living_desc, quality_of_life_desc, safety_desc, crime_asc, health_care_desc, pollution_asc, traffic_asc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over the country name, max 256 characters
pageNoPage number, defaults to 1
sortNoSort enum: name_asc, cost_of_living_asc, cost_of_living_desc, quality_of_life_desc, safety_desc, crime_asc, health_care_desc, pollution_asc, traffic_asc
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
max_crime_indexNoMaximum Crime Index
min_crime_indexNoMinimum Crime Index
min_safety_indexNoMinimum Safety Index
max_traffic_indexNoMaximum Traffic Index
max_pollution_indexNoMaximum Pollution Index
min_health_care_indexNoMinimum Health Care Index
max_cost_of_living_indexNoMaximum Cost of Living Index (New York = 100)
min_cost_of_living_indexNoMinimum Cost of Living Index (New York = 100)
min_quality_of_life_indexNoMinimum Quality of Life Index
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It mentions the dataset source and sort enums but fails to state that the tool is read-only, pagination behavior (though schema has page/page_size), or what the return format is. Significant gaps for a 13-parameter search tool.

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 concise (two sentences plus enum list) with no redundant information. It is front-loaded and efficient, though the structure could be improved by grouping sort values more clearly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 13 parameters, no output schema, and no annotations, the description is insufficient. It explains the dataset source but does not describe output format, filter behavior, or index meanings. Many details are missing for effective use.

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%, so the schema already describes each parameter. The description merely repeats sort enum values already in the schema, adding no extra meaning or context for filtering parameters. Baseline score of 3 is appropriate.

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 the tool searches a composite Numbeo countries dataset with seven index families. The purpose is specific and differentiated from sibling tools like datasets_numbeo_cities_search by name, though it does not explicitly contrast with alternatives.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, such as city-level search or single-country retrieval, nor does it mention prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server