Skip to main content
Glama
telota

bbaw-dse-mcp

by telota

cs_search_for_geonames_id

Find GeoNames IDs for place names to filter correspondences by location. Resolves place names to standard identifiers for correspSearch queries.

Instructions

Search for GeoNames IDs by place name.

PURPOSE: Find GeoNames identifiers for places to use as filters.

WHEN TO USE:

  • When you need a GeoNames ID for correspSearch place filtering

  • To resolve place names to standard identifiers

  • For geographic analysis of correspondence networks

WHEN NOT TO USE:

  • For person or organization names → use search_for_gnd_id()

  • When you already have a GeoNames ID

Args: place_query: Place name to search for (e.g., "Berlin", "Paris") country: Optional ISO-2 country code to restrict search (e.g., "DE", "FR") limit: Maximum number of results to return

Returns: List of dicts with place information: - geonameId: The GeoNames ID (use this for correspSearch) - name: Place name - countryCode: ISO-2 country code - lat, lng: Coordinates - adminName1: First-level admin division (e.g., state) - population: Population count (if available)

Example: >>> results = await search_for_geonames_id("Berlin", country="DE") >>> geonames_id = str(results[0]['geonameId']) >>> letters = await search_correspondences(place_geonames=geonames_id)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
countryNo
place_queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the return format (list of dicts with specific fields), demonstrates usage via an example, and clarifies input constraints. However, it does not mention edge cases like empty results or potential ambiguity, but for a search tool this is adequate transparency.

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?

The description is well-organized with clear headings (PURPOSE, WHEN TO USE, Args, Returns, Example), front-loaded with purpose, and every section adds value. It is appropriately sized given the need to compensate for missing schema descriptions and annotations.

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?

The description covers purpose, usage conditions, parameters, return format, and a concrete example. Given the output schema exists and the tool is a relatively simple search, this is complete. It also distinguishes from related tools effectively, making it comprehensive for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 0% description coverage, but the description's 'Args' section explains each parameter (place_query, country, limit) with clear semantics and examples. This fully compensates for the schema's lack of detail, and the example illustrates proper usage.

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 begins with 'Search for GeoNames IDs by place name', clearly identifying the specific resource and action. It distinguishes from sibling tools by specifying correspSearch filtering and directing users to search_for_gnd_id() for person/organization names.

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?

The 'WHEN TO USE' and 'WHEN NOT TO USE' sections explicitly state the scenarios for using this tool, including alternatives for different entity types and when an ID is already available. This clearly differentiates from sibling tools like cs_search_for_gnd_id.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/telota/bbaw-dse-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server