Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_numbeo_cities_search

Search cities in the Numbeo composite dataset covering seven index families, with range filters on crime, safety, health care, pollution, traffic, cost of living, and quality of life, plus sort options.

Instructions

Search the Numbeo cities dataset. Searches the composite Numbeo cities dataset, merged from the current global rankings of all seven index families (cost of living, quality of life, crime, health care, pollution, traffic, property investment). A city appears once it is ranked by at least one family; coverage varies per city. 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 city 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
countryNoExact country filter, max 128 characters
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
Behavior3/5

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

Since no annotations are provided, the description carries full burden. It discloses that coverage varies per city and that a city appears once ranked by at least one family. However, it doesn't mention pagination constraints, rate limits, or whether the operation is read-only (though assumed).

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 compact (4 sentences) and front-loaded with purpose. Each sentence adds meaningful information without fluff.

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

Completeness3/5

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

With 14 parameters and no output schema, the description covers the dataset purpose and data coverage but does not explain return values or behavior (e.g., response format). Adequate but not complete for a complex tool.

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 baseline 3. The description adds value by explaining the sort enum values and the dataset's composite nature, but most parameters (e.g., min/max indices) are self-explanatory from their names. No additional semantics beyond 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 it searches the Numbeo cities dataset, explains it's a composite of 7 index families, and defines when a city appears. This distinguishes it from sibling tools like datasets_numbeo_cities_item or datasets_numbeo_cities_facets.

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?

The description implies usage for searching/filtering cities but does not explicitly state when to use this tool versus alternatives like datasets_numbeo_cities_facets or other dataset search tools. No when-not or exclusions provided.

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