Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

numbeo_indices_city

Retrieve a Numbeo city's indices for quality of life, crime, health care, pollution, traffic, or property investment, including headline scores and sub-index details.

Instructions

Get a Numbeo city's data for an index family. Returns one city's data for a Numbeo index family (quality of life, crime, health care, pollution, traffic, or property investment): headline indices, and (depending on the family) titled sub-index sections and/or itemized prices.

Input Schema

NameRequiredDescriptionDefault
slugYesNumbeo city slug
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.5/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, but it does disclose what is returned: headline indices plus (family-dependent) sub-index sections and itemized prices. It adds no permission, auth, or rate-limit context, so behavioral coverage is partial.

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, front-loaded with the core action; the parenthetical output detail is informative rather than padding. Slightly wordy with 'index family' used twice but efficient overall.

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?

No output schema exists, so the description usefully outlines the return shape (headline indices, sub-index sections, itemized prices) for a two-parameter read tool. Slug format is left to the schema, which covers it.

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% and the index enum is fully specified in the schema. The description lists the same families, adding marginal reinforcement but no new syntax or format detail, so the baseline of 3 applies.

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?

The description states a specific verb ('Get') and resource ('a Numbeo city's data for an index family') and enumerates the index families, so an agent can distinguish it from country/rankings siblings. It stops short of naming those siblings explicitly.

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 only implied by the scoping ('one city's data'); there is no statement of when to prefer this over numbeo_indices_country, numbeo_indices_rankings, or numbeo_cost_of_living_city, nor any prerequisites.

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