Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_numbeo_cities_item

Retrieve a Numbeo city by slug to access cost of living, rent, quality of life, crime, health care, pollution, traffic, and property indices where ranked.

Instructions

Get a Numbeo city from the dataset. Returns one Numbeo city from the dataset by slug such as Los-Angeles. The record has the city, country, coverage list and the cost of living, rent, quality of life, crime, safety, health care, pollution, traffic and property indices. Indices appear only where the city was ranked.

Input Schema

NameRequiredDescriptionDefault
slugYesNumbeo city slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it enumerates the returned fields (city, country, coverage, and the various indices) and adds a valuable data-completeness caveat ('Indices appear only where the city was ranked'). It omits error behavior for an invalid slug, but for a plain read tool the output disclosure is solid.

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?

Front-loads the core action and is appropriately sized for a one-parameter tool. The first two sentences ('Get a Numbeo city...' / 'Returns one Numbeo city...') are slightly redundant, but the remainder is dense with useful detail.

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 must describe the return value, which it does thoroughly (record fields plus the ranked-only caveat). For a simple single-param lookup this covers everything an agent needs to call and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline would be 3, but the description adds meaning beyond the schema's bare 'Numbeo city slug' by giving a concrete example slug ('Los-Angeles'), clarifying the expected format.

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 a Numbeo city from the dataset') and scopes it to a single record retrieved 'by `slug`', which clearly distinguishes it from a search-style sibling. It does not explicitly name the alternate browse/search tool, but the singular 'one ... by slug' framing makes the item-retrieval intent unambiguous.

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 rather than stated: the agent infers it should call this when it already holds a slug, and the example 'such as Los-Angeles' hints at the required input form. There is no explicit when-to-use versus a search endpoint, nor any exclusion or prerequisite guidance.

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