Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

numbeo_indices_rankings

Fetch global city rankings for a Numbeo index family, either current or historical, to compare cities on quality of life, crime, health care, pollution, traffic, or property investment.

Instructions

Get the global Numbeo city ranking for an index family. Returns the global city ranking for a Numbeo index family, either the continuously-updated current index or a historical periodic snapshot.

Input Schema

NameRequiredDescriptionDefault
indexYesIndex family
scopeNocurrent (default) or historical
periodNoRequired when scope=historical, e.g. 2026-mid or 2025

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / index / enum
      Added value: +[
+  "quality-of-life",
+  "crime",
+  "health-care",
+  "pollution",
+  "traffic",
+  "property-investment"
+]
    • addedInput schema / properties / scope / enum
      Added value: +[
+  "current",
+  "historical"
+]
  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 full burden. It discloses the temporal nature ('continuously-updated current index or a historical periodic snapshot'), which adds useful context, and implies a read operation. However it says nothing about return format or how the ranking is ordered, leaving gaps for an unannotated 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?

Two sentences that are appropriately short and front-load the core action. The second sentence largely restates the first ('global city ranking for an index family'), introducing mild redundancy, but overall it is compact and readable.

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 simple read ranking tool with full schema coverage and no output schema, the description covers purpose and the current/historical split adequately. What is missing is placement relative to the sibling Numbeo tools, but nothing essential to invoking the tool is absent.

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 enum values and the period requirement are already documented in the schema. The description reinforces the current/historical distinction but adds no syntax or format detail beyond what the schema provides, so baseline 3 is appropriate.

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 city ranking for an index family') with clear scope. An agent can distinguish it from numbeo_indices_city (single city) and numbeo_indices_rankings_by_country (country level) by the 'global city ranking' wording. It doesn't explicitly name those siblings, 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?

Usage is implied through the mention of current vs historical snapshots, which maps to the scope parameter, but there is no explicit when-to-use guidance or routing to alternatives like numbeo_indices_city. The agent must infer when this ranking tool is preferable to the single-city or country variants.

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