wikipedia-mcp-server

Search Wikipedia Nearby

wikipedia_search_nearby

Read-only

Find Wikipedia articles about places near a geographic coordinate. Returns articles sorted by distance from the query point, with titles, page IDs, coordinates, and distance in meters. Useful for "what is notable near X?" research workflows. Only articles with geographic coordinates in their Wikidata record are returned — not all articles about locations are geotagged.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results to return (default 10, max 500 — the MediaWiki geosearch ceiling). Must be a positive integer. Geosearch has no pagination, so articles past this limit are only reachable by raising it or searching narrower radii.
`language`	No	Wikipedia language edition code (default "en"). Examples: "fr", "de", "ja".	en
`latitude`	Yes	WGS 84 latitude in decimal degrees (range: −90 to 90).
`longitude`	Yes	WGS 84 longitude in decimal degrees (range: −180 to 180).
`radius_meters`	No	Search radius in meters (default 1000, min 10, max 10000 — the MediaWiki geosearch bounds). Must be an integer; a value above the maximum is clamped to it.

Output Schema

TableJSON Schema

Name	Required	Description
`cap`	No	The limit that was applied.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Number of results returned.
`notice`	No	Guidance when results were capped (raise limit or sweep narrower radii) or when no geotagged articles were found (increase radius). Absent when neither applies.
`results`	No	Geotagged articles sorted ascending by distance_meters.
`language`	No	Language edition queried.
`truncated`	No	True when more articles matched than the limit allowed. Established by probing one result past the limit, so a match count landing exactly on the limit reports false.
`queryLatitude`	No	Latitude used for the search.
`queryLongitude`	No	Longitude used for the search.
`radiusMetersUsed`	No	Radius in meters used for the search.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the description's job is to add context beyond that. It discloses the geotag requirement (only articles with coordinates), which is a non-obvious behavior, and describes the sort order and return fields. This adds value without contradicting the annotations.

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 purpose and return details, then a concise usage hint and caveat. Zero fluff; every clause earns its place.

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?

With a rich schema covering all parameters and an output schema present, the description covers the essential behavioral aspects: what it returns, sorting, and the geotag limitation. Annotations handle safety and open-world expectations. An agent has everything needed to call this tool correctly.

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% — every parameter (limit, language, latitude, longitude, radius_meters) has a detailed description with defaults, ranges, and constraints. The tool description adds no parameter-specific meaning beyond what the schema already provides, so the baseline 3 is appropriate.

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 (Find) and resource (Wikipedia articles) with a clear scope (near a geographic coordinate), and explicitly describes the output (titles, page IDs, coordinates, distance in meters). This clearly distinguishes it from text-based search tools like wikipedia_search_articles and article retrieval like wikipedia_get_article.

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?

Provides a clear use case ('what is notable near X?' research workflows) and notes a key limitation (only articles with coordinates in Wikidata are returned). However, it does not explicitly name alternatives or state when not to use it, relying on the purpose to imply context.

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

All wikipedia-mcp-server 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.