Skip to main content
Glama

Country State City

by io.github.pipeworx-io

Pipeworx Trending

pipeworx_trending
Read-onlyIdempotent

What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking your own question, (3) seeing whether your use case aligns with what most agents need. Self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count). Cached 5min-1h depending on window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNo24h (default) | 7d | 30d. Shorter windows surface what's hot right now; longer windows show steady-state demand.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds valuable behavioral details beyond annotations: no PII, derived from CF analytics-engine, cached 5min-1h depending on window, and returns specific fields (pack, tool, count). This fully discloses behavior.

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 exceptionally concise: three sentences plus a bullet list of use cases. Every sentence adds value, no fluff. Front-loaded with the core purpose, then expands on use and implementation details.

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 one optional parameter and no output schema, the description is thorough: it states the return type (top tools, packs, volume), use cases, data source, privacy, caching behavior, and window interpretation. Nothing essential is missing.

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 coverage is 100%; the only parameter 'window' has enum values described. The description adds meaning beyond the schema, explaining the trade-off between short and long windows. This provides pragmatic guidance.

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 clearly states it returns top tools, packs, and total call volume over recent windows. The verb 'returns' and resource 'trending data' are specific. It distinguishes from siblings like discover_tools and ask_pipeworx by focusing on trends and popularity.

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?

The description explicitly lists three use cases: discovering hot data sources, confirming canonical choices, and checking alignment with other agents' needs. It also explains window trade-offs ('shorter windows surface what's hot right now; longer windows show steady-state demand'). While it does not directly name alternatives, the context is clear and well-motivated.

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

All Country State City 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.7/5.0
Disambiguation2/5

Several tools overlap enough to cause misselection: ask_pipeworx and ask_pipeworx_beta are functionally identical right now, ask_pipeworx_grounded and validate_claim both handle factual lookup/verification, and ai_visibility_check/scan_competitor_ai_presence are near duplicates in scope. The country/state/city tools are distinct but sit in a pile of unrelated Pipeworx tools, adding confusion.

Naming Consistency3/5

All names are lower_snake_case and families like polymarket_* and ask_pipeworx* help group tools, but the verb_noun convention is inconsistent: entity_profile, deep_research, recent_alerts, and pipeworx_trending are noun phrases, while remember/forget/subscribe are bare verbs. It is readable but not a predictable pattern.

Tool Count2/5

34 tools is above the practical ceiling for a focused MCP server, and the mismatch is severe: only 3 tools match the 'Country State City' name while 31 belong to a broad Pipeworx platform. A geographic server would need roughly 3-6 focused tools; this surface is bloted.

Completeness2/5

For the stated Country State City domain, list_countries/get_states/get_cities provide the basic hierarchy, but there is no city search, country/state detail lookup, or attribute discovery beyond the three list endpoints, making the useful geographic surface thin. For the Pipeworx domain the coverage is broader, but that confirms the identity mismatch and obscures the server's actual purpose.

Resources