Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

numbeo_indices_city

Fetch a city's Numbeo data by index family: quality of life, crime, health care, pollution, traffic, or property investment, including headline indices, sub-sections, and itemized prices.

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

Input Schema

TableJSON 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

A4/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 burden. It discloses that the data is credential-free public Numbeo data, which is useful context. However, it doesn't describe the exact return structure beyond mentioning headline indices, sub-index sections, and itemized prices, nor does it mention potential variability in response shape across index families.

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 compact and front-loaded: it states the action, the resource, the scope, and the data source in two sentences. Every sentence earns its place, and the credential-free note is a useful addition without bloat.

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 two-parameter read tool with no output schema, the description is nearly complete. It explains what data comes back (headline indices, sub-index sections, itemized prices) and the public nature of the data. It could mention that the response shape varies by index family, but the description already hints at this with 'depending on the family'.

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. The description adds the list of index families and the notion of 'headline indices' and 'sub-index sections', but doesn't add meaning beyond what the schema provides. Baseline 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 states a specific verb ('Get'), a specific resource ('a Numbeo city's data for an index family'), and enumerates the exact index families. It also distinguishes itself from the sibling numbeo_indices_rankings_by_country by focusing on a single city's data rather than country rankings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies when to use this tool: when you need one city's data for a specific index family. It doesn't explicitly name the alternative numbeo_indices_rankings_by_country or state when not to use it, but the scope is clear enough that an agent can infer the distinction.

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