Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

numbeo_cost_of_living_rankings

Retrieve global cost-of-living city rankings by current or historical period, covering Cost of Living, Rent, Groceries, Restaurant Price, and Local Purchasing Power indices.

Instructions

Get the global Numbeo cost-of-living city ranking. Returns the global cost-of-living city ranking (Cost of Living, Rent, Cost of Living Plus Rent, Groceries, Restaurant Price, and Local Purchasing Power indices), either the continuously-updated current index or a historical periodic snapshot.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / scope / enum
      Added value: +[
+  "current",
+  "historical"
+]
  2. Addedv1.5.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that this is a read-style operation, what indices are returned, and that data is either continuously updated or a periodic snapshot. It does not state whether the ranking is paged, how many cities are returned, or any caching/freshness caveats.

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 with the core purpose front-loaded and the mode distinction following. Slightly repetitive in restating 'global cost-of-living city ranking' twice, but overall tight and free of filler.

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?

No output schema exists, and the description does cover the returned index fields, which is helpful. For a parameter-light read tool this is largely complete, but the lack of any sibling disambiguation among the many numbeo rankings tools leaves an important gap.

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 both parameters, establishing a baseline of 3. The description adds some meaning by characterizing 'current' as a continuously-updated index versus 'historical' as a periodic snapshot, but provides no format detail beyond the schema's example ('2026-mid or 2025').

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 clear verb ('Get') and specific resource ('global Numbeo cost-of-living city ranking') and lists the returned indices, so the agent knows what it produces. However, it does not distinguish itself from the multiple numbeo siblings, notably numbeo_cost_of_living_rankings_by_country, numbeo_indices_rankings and numbeo_indices_rankings_by_country, so the agent must infer the difference from the name alone.

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 the two scope modes (current vs historical) but gives no explicit guidance on when to choose this tool over the several sibling rankings tools. No exclusions, prerequisites, or alternative routing are provided, so usage is left to inference from the name.

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