Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_numbeo_cities_search

Search Numbeo city rankings by name or country, then sort and filter cost of living, quality of life, crime, health care, pollution, traffic, and property investment indexes.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "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"
+]
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior4/5

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

No annotations exist, but the description reveals important behavior: results come from a merged dataset, cities appear once ranked by any family, and coverage varies by city. This goes beyond the schema and helps agents interpret sparse results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are somewhat redundant ('Search...' / 'Searches...'), and the sort enum duplicates the schema. Still compact and front-loaded with dataset context.

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?

For a 14-parameter search tool with no output schema, the description explains dataset composition and coverage but doesn't describe result shape, pagination behavior beyond schema, or why some index families have no sort/filter options. Adequate but with clear gaps.

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 describes all 14 parameters at 100% coverage, including the sort enum. The description mostly repeats the enum rather than adding new semantic meaning, so it earns the baseline rather than credit for compensation.

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?

Description uses specific verb 'Search' and names 'Numbeo cities dataset', then clarifies it is a composite merged from seven index families. It doesn't explicitly compare with sibling tools like datasets_numbeo_cities_facets or numbeo_indices_rankings_by_country, so it stops short of a 5.

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 text implies this is for querying city-level data across multiple indices, and the coverage caveat helps set expectations. It provides no explicit when-to-use/when-not-to-use guidance or named alternatives.

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

Deploy Server

Other Tools