Skip to main content
Glama

Geonames

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.7/5.0
Behavior5/5

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

Discloses beyond annotations: key-value scoped by identifier, persistent for auth users, 24-hour for anonymous. Annotations provide idempotentHint and destructiveHint, description adds context.

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?

Four concise sentences. Front-loaded with purpose. No redundancy or fluff.

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 tool with two string params and no output schema, description covers all essential: usage context, pairing, scoping, persistence. No gaps.

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 has 100% coverage with descriptions for key and value. Description adds examples but doesn't introduce new semantic constraints beyond schema.

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?

Clearly states verb 'Save data' and resource 'key-value pair'. Specifies scope: across conversation or sessions. Examples (ticker, address, preference) distinguish from siblings recall and forget.

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?

Explicitly says when to use: when discovering something worth carrying forward. Lists pairs with recall and forget, and mentions scoping by identifier and persistence duration.

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

All Geonames toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded; multiple polymarket_* scanners), and the mix of unrelated domains makes it hard to tell which tool is canonical for a task. The few geographic tools are distinct, but they are buried among dozens of non-geographic tools.

Naming Consistency2/5

Naming is a mix of verb_noun (search_geonames, resolve_entity), proper-noun prefixes (pipeworx_*, polymarket_*), and descriptive phrases (ask_pipeworx, bet_research, scan_competitor_ai_presence). No consistent pattern or verb style across the set.

Tool Count2/5

35 tools is far more than a Geonames-focused server needs, and most are unrelated to geospatial data. The count would be borderline for a general data platform, but it is excessive and unfocused for the stated server name.

Completeness1/5

The geographic surface is severely incomplete: only four tools (search_geonames, get_nearby, find_postal_codes, get_timezone) cover a tiny sliver of typical Geonames functionality like reverse geocoding, elevation, or distance calculations. The many non-geographic tools do not compensate for the missing core domain coverage.

Resources