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 Numbeo index families like quality-of-life, crime, or health-care, for current or historical periods. Uses credential-free public Numbeo data.

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. Credential-free public Numbeo data (numbeo.com).

Input Schema

TableJSON 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?

With no annotations, the description must carry the full burden of behavioral disclosure. It mentions the data is credential-free and public, and that results are either current or historical snapshots. However, it does not describe the output structure, pagination, or any limitations, which is a notable gap for a tool with no output schema.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the primary purpose, and contains no fluff. Every sentence contributes meaning: the first states the action, the second elaborates on modes and data source.

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?

The tool is moderate in complexity with three parameters and no output schema. The description explains the two modes and data provenance but does not specify the return format (e.g., whether it's a full list or top-N, or how results are ordered). This incomplete context could leave an agent uncertain about the tool's output.

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?

The input schema provides 100% coverage of all parameters, including enums and descriptions. The tool description adds marginal context (e.g., 'continuously-updated current index or a historical periodic snapshot' mapping to scope) but does not explain the period format beyond what the schema already states, so the baseline of 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?

The description clearly states a specific action ('Get the global Numbeo city ranking') and resource (index family), and distinguishes it from country-level ranking tools by specifying 'global city ranking'. It also conveys the two modes (current/historical) and the data source, leaving no ambiguity about what the tool does.

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 does not explicitly mention when to use this tool versus alternatives like numbeo_indices_rankings_by_country or numbeo_indices_city. It implies city-level rankings but fails to contrast with sibling tools, leaving the agent to infer the right selection.

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