Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

numbeo_indices_rankings_by_country

Retrieve global Numbeo country rankings for a chosen index family, including quality-of-life, crime, health-care, pollution, traffic, and property-investment, with ranks and named index values.

Instructions

Get the global Numbeo country ranking for an index family. Returns the global Numbeo ranking of countries for one index family, selected by the required index: quality-of-life, crime, health-care, pollution, traffic or property-investment. Each row has its rank, country and a list of named index values, such as the Crime Index and Safety Index for crime.

Input Schema

NameRequiredDescriptionDefault
indexYesIndex family

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / index / enum
      Added value: +[
+  "quality-of-life",
+  "crime",
+  "health-care",
+  "pollution",
+  "traffic",
+  "property-investment"
+]
  2. Addedv1.5.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the return shape: one row per country with `rank`, country, and named index values (e.g. Crime Index and Safety Index for `crime`). It does not mention authentication, rate limits, or freshness/date of the ranking data, which is a gap for a data-source 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?

Three sentences, front-loaded with the purpose. The first sentence ('Get the global Numbeo country ranking for an index family') is essentially restated by the opening clause of the second ('Returns the global Numbeo ranking of countries for one index family'), a mild redundancy, but the rest earns its place by enumerating values and return fields.

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 single-parameter tool with no output schema, the description supplies the enum options and the per-row return structure, which is what an agent needs to invoke and interpret it. Missing only ancillary context such as data recency or whether rankings cover all countries.

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% and the enum already lists all six index families, so the description largely repeats structured data. It does add marginal meaning by illustrating that a chosen family yields multiple named sub-indices (Crime + Safety for `crime`), but that is a small increment over the schema.

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?

States a specific verb and resource ('Get the global Numbeo country ranking for an index family') and the scope is unambiguous — country-level rankings, as opposed to the sibling numbeo_indices_country (per-country index values) or numbeo_indices_rankings (city rankings). It does not name those siblings explicitly, so an agent must infer the distinction from the scope wording.

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?

Usage is implied by the scope: use this when you want a global country ranking for one index family. There is no explicit when-to-use/when-not guidance, no mention of the alternative numbeo_indices_rankings or numbeo_indices_country, and no prerequisites or rate-limit notes.

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