MCP NewsAPI.ai

suggest_locations

Read-only

Resolve a city or country name to a location URI for filtering article and event searches. Locate news tied to that area without using search tokens.

Instructions

Resolve a city or country name to a location URI. Pass the uri as location_uris to search_articles / search_events to find news that happened there. Does not consume search tokens.

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": {
      "prefix": "<prefix>"
    },
    "name": "suggest_locations"
  }
}

Input Schema

Name	Required	Description
`lang`	No	Language of the prefix, ISO 639-3 (default eng).
`page`	No	Result page, from 1 (default 1).
`count`	No	Max suggestions, 1-50 (default 10).
`prefix`	Yes	Text typed so far (a name or the start of one), e.g. "Telef" or "bbc".

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations cover only readOnlyHint=true; the description adds genuinely useful behavioral context beyond that ('Does not consume search tokens') and clarifies the return type is a location URI, which matters for a resolver tool. It omits pagination/limit nuance, but the token-cost note is a meaningful addition.

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 tight sentences, front-loaded with purpose, followed by the integration path and the token-cost caveat. No filler.

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 no output schema, the description correctly explains what is returned (a location URI) and how to use it, plus the token-cost trait. It is complete enough to invoke correctly, missing only edge-case behavior (empty results, pagination).

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 lang, page, count and prefix are already documented with defaults and ranges. The description only references the output `uri`, adding nothing about input parameter semantics; baseline 3 applies.

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 gives a precise verb+resource ('Resolve a city or country name to a location URI') and immediately names the siblings that consume the result. An agent can distinguish this from suggest_concepts/suggest_categories/suggest_sources without opening any schema.

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?

Explicitly states the usage path: pass the returned `uri` as `location_uris` to search_articles/search_events. It gives clear context for when to reach for this tool, though it does not state when NOT to use it or how it differs from the other suggest_* tools.

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

Deploy Server