City Data Lookup SkillCity Data Lookup Skill

OnlineCredit Usage:1 per callTool:CityDataLookupSkill

The tool

Let your agent resolve any city to its population, country and coordinates. Call it as an MCP tool to add place data across 150K+ cities.

Once your client is connected to the VerveKit MCP server, this appears in its tool list as CityDataLookupSkill. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.

Tool call
{
  "name": "CityDataLookupSkill",
  "arguments": {
    "city": "San Francisco"
  }
}

What that looks like in a conversation

You don't name the tool — the model picks it. Asking about San Francisco in the terms this source covers is enough for it to reach for CityDataLookupSkill on its own.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.

Client config
{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}
Endpoint
https://api.vervekit.com/v1/mcp

Per-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made.

ArgumentTypeExampleDescription
cityRequiredstringSan FranciscoThe city name for which you want to get the data (e.g., New York)
limitPremiuminteger5Limit number of cities that match your search criteria

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "search": "San Francisco",
    "foundCities": [
      {
        "name": "San Francisco",
        "altName": "",
        "country": "US",
        "countryName": "United States",
        "featureCode": "PPLA2",
        "population": 874961,
        "populationCategory": "major",
        "loc": {
          "type": "Point",
          "coordinates": [
            -122.4194,
            37.7749
          ]
        }
      }
    ]
  }
}

Fields

FieldTypeExampleDescription
searchstringSan FranciscoThe search query used to find cities
foundCitiesarray[1]list of rowsArray of city objects matching the search criteria
foundCities.0.namestringSan Francisco
foundCities.0.altNamestring
foundCities.0.countrystringUS
foundCities.0.countryNamestringUnited States
foundCities.0.featureCodestringPPLA2
foundCities.0.populationnumber874961
foundCities.0.populationCategorystringmajor
foundCities.0.locobject{…}
foundCities.0.loc.typestringPoint
foundCities.0.loc.coordinatesarray[-122.4194,37.7749]

Failure modes

Errors come back as tool errors with a sentence the model can act on, not a bare status code.

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This skill isn't part of VerveKit. Check the catalog.
429Brief rate limit. Retrying after a moment succeeds.

Other ways to use City Data Lookup Skill

Set up City Data Lookup Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an X-API-Key header, with SDKs for Node, Python and .NET.APIVerveReference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContextReference →

Frequently asked questions

Do I have to tell the agent to use CityDataLookupSkill?

No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.

Does connecting the server expose every tool at once?

Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.

What does a call cost?

1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.

Is there a REST version of this?

Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?