Skip to main content
Glama

Numbeo cost-of-living prices for one city from its public

travel_numbeo
Read-only

Numbeo cost-of-living prices for one city from its public page: item label and the crowd-sourced price with currency symbol (e.g. meal at an inexpensive restaurant, one-way ticket). Prices are user-submitted estimates, not official. Related tools on this server, for a different need: travel_hostelworld when you need Hostels in a city as listed on Hostelworld's public city; travel_momondo when you need momondo flight prices from its public route page for two. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>"
    },
    "name": "travel_numbeo"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name as Numbeo writes it, e.g. Paris or New-York (letters, spaces, hyphens, 2 to 60 characters)
limitNoMax items, 1 to 100 (default 10)

Output Schema

NameRequiredDescriptionDefault
cityNo
countNo
itemsNo
sourceNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses that prices are user-submitted crowd-sourced estimates rather than official figures, which is material for trusting the output. It also states the billing model ($0.002 per successful call via x402 across USDC/Base and other networks) and that failed calls are not charged.

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?

The core purpose and output shape are front-loaded in the first clause, followed by the data-quality caveat and then routing to alternatives. The billing sentence is long but carries decision-relevant cost information; minor redundancy appears in repeating 'from its public page.'

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values need not be described, and the description still sketches the result shape. With only two well-documented parameters, a read-only annotation profile, pricing, and data-quality caveats all covered, nothing an agent needs before calling is missing.

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 both parameters (city format and limit range) are already documented, setting a baseline of 3. The description adds only marginal meaning beyond that — the currency-symbol output convention and item examples clarify what the inputs yield rather than redefining the parameters.

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 resource (Numbeo cost-of-living prices for one city) and the exact shape of the result set: item label plus crowd-sourced price with currency symbol, with concrete item examples. An agent can distinguish it from hostel or flight-price siblings without opening the schema.

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

Usage Guidelines5/5

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

It names two specific alternatives and the condition that selects each one (travel_hostelworld for hostels, travel_momondo for momondo flight prices for two), framing them as 'a different need.' The implicit when-to-use for this tool — cost-of-living item prices for a single city — is unambiguous from that contrast.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources