Crawlora MCP

datasets_numbeo_cities_facets

Read-only

Returns terms aggregation counts for the Numbeo cities dataset, honoring the same filters as Search the Numbeo cities dataset. Use alongside the related search tool to inspect filter counts under the same query filters.

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": {
      "facet": "<facet>"
    },
    "name": "datasets_numbeo_cities_facets"
  }
}

Input Schema

Name	Required	Description
`q`	No	Optional full-text query over the city name, max 256 characters.
`page`	No	Result page number, 1-based, default 1; page times page_size must not exceed 10000.
`sort`	No	Optional sort order. Allowed values: name_asc, cost_of_living_asc, cost_of_living_desc, quality_of_life_desc, safety_desc, crime_asc, health_care_desc, pollution_asc, traffic_asc. Defaults to relevance with q, otherwise name_asc.
`facet`	Yes	Required facet to aggregate. Allowed values: country.
`country`	No	Optional exact country filter, max 128 characters.
`page_size`	No	Page size, default 20, max 100; page times page_size must not exceed 10000.
`max_crime_index`	No	Optional maximum Crime Index.
`min_crime_index`	No	Optional minimum Crime Index.
`min_safety_index`	No	Optional minimum Safety Index.
`max_traffic_index`	No	Optional maximum Traffic Index.
`max_pollution_index`	No	Optional maximum Pollution Index.
`min_health_care_index`	No	Optional minimum Health Care Index.
`max_cost_of_living_index`	No	Optional maximum Cost of Living Index (New York = 100).
`min_cost_of_living_index`	No	Optional minimum Cost of Living Index (New York = 100).
`min_quality_of_life_index`	No	Optional minimum Quality of Life Index.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the useful constraint that it honors the same filters as the search tool, but says nothing about the return shape or aggregation behavior beyond the generic 'terms aggregation counts'.

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?

Two sentences, front-loaded with the core behavior and immediately followed by the usage cue. No padding or restatement of the name.

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?

With an output schema, complete parameter documentation, and annotations carrying the safety profile, the description only needs to establish purpose and usage, which it does. It could optionally note which facet dimensions are aggregatable, but the schema already constrains facet to 'country'.

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 all 15 parameters are already documented, including the required 'facet' enum value and the index-range filters. The description adds only the high-level note that filter semantics match the search tool, which is context rather than new per-parameter detail.

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: 'Returns terms aggregation counts for the Numbeo cities dataset.' It differentiates from the sibling by framing itself as the facets companion to 'the related search tool,' though it does not name datasets_numbeo_cities_search explicitly.

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?

'Use alongside the related search tool to inspect filter counts under the same query filters' clearly conveys the scenario for calling it, and 'honoring the same filters as Search the Numbeo cities dataset' ties it to the companion query. No explicit exclusions, but the intended use is unambiguous.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?