Skip to main content
Glama

Geonames

by io.github.pipeworx-io

Send Pipeworx Feedback

pipeworx_feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a claim_token; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNobug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
contextNoOptional structured context: which tool, pack, or vertical this relates to.
messageNoYour feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_tokenNoRead the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

TDQS

A5/5.0
Behavior5/5

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

The description discloses follow-up behavior (claim_token for checking resolution status), rate limits (5 per identifier per day), roadmap impact, and the fact that it's free. These details go well beyond the sparse annotations (all false hints) and there is no contradiction.

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 concise despite its length: each sentence carries unique information, structured logically from purpose to usage to exclusions to follow-up. It front-loads the core purpose and avoids redundancy.

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 tool with 4 parameters, nested objects, no output schema, and sparse annotations, the description is remarkably complete. It covers purpose, usage boundaries, parameter behavior, token lifecycle, and operational constraints, leaving no meaningful questions unanswered.

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?

Although the schema has 100% parameter descriptions, the tool description enriches semantics: it explains how claim_token is used ('pass it back later as pipeworx_feedback({claim_token:"pwfb_…"})'), instructs users to describe issues in terms of Pipeworx tools, and clarifies the context object's purpose—adding value beyond the raw 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?

The description opens with a specific action—'Tell the Pipeworx team something is broken, missing, or needs to exist'—and clearly enumerates the feedback types (bug, feature/data_gap, praise). It names the resource (Pipeworx tools) and differentiates from sibling research tools by being the only feedback channel.

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 guidance is given: 'Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise).' It also includes an exclusion criterion—'ONLY for tools served by this Pipeworx connection'—and directs users to file with the correct server otherwise.

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