Skip to main content
Glama
telota

bbaw-dse-mcp

by telota

cs_get_place_geonames_id

Get the GeoNames ID for any place by providing its name. Useful for quick lookups when you only need the identifier.

Instructions

Get the GeoNames ID for a place (convenience function).

PURPOSE: Quick lookup of a single GeoNames ID for a place.

WHEN TO USE:

  • When you just need the ID without details

  • For quick place-to-ID conversion

  • When you're confident about the place name

WHEN NOT TO USE:

  • When the place name might be ambiguous → use search_for_geonames_id()

  • When you need full place details

Args: place_name: Name of the place (e.g., "Berlin", "Paris") country: Optional ISO-2 country code to restrict search (e.g., "DE")

Returns: GeoNames ID as integer, or None if not found

Example: >>> berlin_id = await get_place_geonames_id("Berlin", country="DE") >>> # Returns: 2950159 >>> letters = await search_correspondences(place_geonames=str(berlin_id))

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNo
place_nameYes

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 transparency burden. It discloses that it returns an integer or None if not found, which is critical behavioral information. The example also illustrates usage. It does not discuss errors or side effects, but for a simple lookup this is sufficient.

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 sections (PURPOSE, WHEN TO USE, WHEN NOT TO USE, Args, Returns, Example). Every sentence adds value, and the structure makes information easy to scan.

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 simple lookup tool, the description provides all needed context: purpose, usage guidance, return behavior, parameter semantics, and a concrete example. An output schema exists but the description clarifies what is returned, making it complete.

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?

Schema provides no parameter descriptions (0% coverage), but the description includes an Args section explaining 'place_name' with examples and 'country' as an optional ISO-2 code restricting search. This fully compensates for the schema gaps.

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?

Description clearly states it gets a GeoNames ID for a place, distinguishing it as a quick lookup from cs_search_for_geonames_id which handles ambiguity. The verb 'Get' and resource 'GeoNames ID' are specific, and the convenience function framing sets expectations.

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?

Explicit WHEN TO USE and WHEN NOT TO USE sections provide clear guidance. It names the alternative tool for ambiguous names, making the decision process straightforward.

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