Skip to main content
Glama

Country State City

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare safe read-only behavior; description adds scoping detail (identifier-based) without contradicting annotations.

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?

Three concise sentences, front-loaded with main purpose, no wasted words.

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?

Simple tool with one optional parameter, no output schema needed; description fully covers use cases, scoping, and companion tools.

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

Parameters4/5

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

Schema covers 100% of the single parameter; description adds value by explaining the dual behavior of retrieving a specific key vs. listing all when omitted.

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 the tool retrieves a value by key or lists all keys, distinguishing it from sibling tools like remember 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly describes when to use (look up stored context) and pairs with remember/forget, but does not state explicit when-not-to-use scenarios.

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