Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_numbeo_countries_item

Retrieve a Numbeo country profile by exact country name to access coverage and ranked indices for cost of living, rent, quality of life, crime, safety, health care, pollution, traffic, and property.

Instructions

Get a Numbeo country from the dataset. Returns one Numbeo country from the dataset by country, spelled as Numbeo does, such as Vietnam. The record has a coverage list and country-level indices for cost of living, rent, quality of life, crime, safety, health care, pollution, traffic and property, present only where ranked.

Input Schema

NameRequiredDescriptionDefault
countryYesCountry name as Numbeo spells it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does disclose useful behavior: the returned record contains a `coverage` list plus specific country-level indices, and these are present only where ranked. That 'present only where ranked' caveat is genuine behavioral context an agent would otherwise miss; auth/rate-limit details are unnecessary for a static dataset lookup.

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?

Three sentences, front-loaded with purpose, then keying, then return shape. Minor redundancy in repeating 'from the dataset' across the first two sentences, but overall tight and well-ordered.

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 one-parameter dataset lookup with no output schema and no annotations, the description covers purpose, keying convention, and the returned record contents. It does not say what happens when the country is not found or whether a search step is required first, but it is otherwise complete.

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 coverage is 100% and the schema already states 'Country name as Numbeo spells it'. The description reinforces the exact-spelling requirement with a concrete example ('Vietnam'), which adds marginal value but stays near the baseline set by the fully-covered schema.

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 country from the dataset') and specifies it returns exactly one country keyed by name. It clearly reads as a single-item lookup, distinct from the sibling datasets_numbeo_countries_search, though it never names that alternative explicitly.

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?

There is no explicit when-to-use guidance and no mention of the sibling search/facets tools for discovering valid country values. Usage is only implied: call it when you already know the Numbeo-spelled country 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