Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_numbeo_countries_search

Search the Numbeo countries dataset. Searches the composite Numbeo countries dataset, merged from the current global by-country rankings of all seven index families.

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. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input 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

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.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and it delivers the single most important behavioral fact: credit-based billing (1 credit per record, minimum 2, empty result still costs 2, full page 100). That cost model materially affects how an agent selects page_size and issues calls. It does not, however, disclose auth requirements or rate limits.

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?

Three tightly front-loaded sentences: identity, composition, then billing. The only waste is re-listing the nine sort values already present in the schema enum, but the billing sentence that follows earns its place.

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?

For a 13-parameter, zero-required search with no output schema and no annotations, the description covers dataset identity and the cost model that the structured fields cannot express. The index-filter semantics (max_crime_index, min_safety_index, etc.) are left entirely to the schema, which is acceptable given 100% coverage but leaves the description slightly thin on filtering intent.

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 description coverage is 100%, so the schema already documents all 13 parameters with enums and ranges. The description's sort enum list is a verbatim duplicate of the schema enum and adds no syntax or semantic detail, so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Search the Numbeo countries dataset') and clarifies the dataset is a composite merged from the global by-country rankings of all seven index families. This lets an agent distinguish it from datasets_numbeo_cities_search and datasets_numbeo_countries_item without opening the schema.

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?

The description explains what the dataset contains but gives no when-to-use or when-not-to-use guidance, and never names the natural alternatives (datasets_numbeo_cities_search for city-level data, datasets_numbeo_countries_item for a single country). Usage is only implied.

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