Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_numbeo_countries_search

Search Numbeo countries by name, cost of living, safety, crime, health care, pollution, traffic, and quality of life, with sorting and index-based filters.

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

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
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully explains that the dataset is composite and merged from current global by-country rankings of all seven index families, which clarifies the data scope. However, it does not disclose pagination behavior, whether all countries are returned when no query is supplied, or what the response contains beyond the implied index rankings.

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 description is short and front-loads the core purpose, but the first two sentences are partially redundant: 'Search the Numbeo countries dataset' and 'Searches the composite Numbeo countries dataset' repeat the same idea. The sort enum list is long and duplicates the schema, though it is useful for quick reference.

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 13-parameter search tool with no output schema, the description gives the essential dataset context and available sort dimensions but stops short of describing result semantics or default behavior. The composite dataset explanation reduces some ambiguity, but a more complete description would clarify what a returned country record contains and how search behaves without a query.

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 and the baseline is 3. The description adds context by naming the seven index families and repeating the sort enum, but it does not meaningfully explain any parameter beyond what the schema provides. It helps frame the index-related filters but is not essential.

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 identifies a specific action (search) and resource (the Numbeo countries dataset), and adds that it is a composite dataset merged from all seven index families. This differentiates it from sibling item-lookup tools like datasets_numbeo_countries_item and from per-index ranking tools. The purpose is immediately obvious to an agent.

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 the tool is for searching the composite Numbeo countries dataset, but it does not explicitly say when to prefer this tool over alternatives such as datasets_numbeo_countries_item or the individual numbeo ranking tools. There is no mention of exclusions, prerequisites, or a recommended fallback. Usage context is present but left to inference.

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