Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fever_top_cities

Retrieve Fever's fixed seed list of 25 cities with IDs, codes, coordinates, and thumbnails; use it to seed city-based lookups or confirm covered cities.

Instructions

List Fever's fixed top-city seed. Returns Fever's (feverup.com) fixed list of 25 top cities, in the upstream's own order, with each city's id, code, name, country, region, slug, language, centre coordinates and thumbnail. This is the only enumerable city surface on the platform: it is a top list and not the complete city set, so use fever-cities to find a city outside it. It takes no parameters and has no paging.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fever_top_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.7/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 behavioral burden and does well: it discloses fixed ordering, a hard cap of 25, partial coverage of the city universe, no parameters and no paging. It stops short of saying whether the list is cached/static across calls or what an empty/failed response looks like, which keeps it below 5.

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?

Three sentences, front-loaded with the core purpose, then return shape, then routing guidance. Every sentence earns its place and nothing is repeated from the schema.

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?

For a zero-parameter list tool with no output schema, the description compensates by naming every returned field and the ordering guarantee, and by warning that the set is not exhaustive. Nothing an agent needs in order to call it and interpret the result 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?

Zero parameters, so the baseline is 4; the description reinforces this with "takes no parameters and has no paging," which usefully rules out paginating an agent might otherwise attempt. There is no parameter semantics left to add.

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?

States a specific verb and resource ("List Fever's fixed top-city seed"), then enumerates exactly what is returned (25 cities with id, code, name, country, region, slug, language, coordinates, thumbnail) in upstream order. It also explicitly separates itself from fever_cities, so an agent can choose between them without opening either 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?

Gives both a use case (enumerating the fixed top list) and an explicit exclusion with a named alternative: "it is a top list and not the complete city set, so use fever-cities to find a city outside it." That is as close to when/when-not routing as a description gets.

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