Skip to main content
Glama

Geonet Nz

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds scoping details (user identifier) beyond annotations, which is useful behavioral 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?

Description is three concise sentences, front-loaded with the core action, followed by use case and scoping. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple interface (1 param, no output schema), description covers purpose, usage, scoping, and sibling relationships. Could explicitly mention return format (value or list).

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 covers the sole parameter with clear description. The tool description reiterates the omit-to-list behavior but does not add new semantic information beyond the 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?

Description clearly states the tool retrieves a value by key or lists all keys. It specifies the resource (values saved via remember) and distinguishes from siblings 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 says when to use (look up stored context), and mentions pairing with remember/forget. Could be more explicit about when not to use, but overall provides solid guidance.

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

All Geonet Nz 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.9/5.0
Disambiguation2/5

Several tools are deliberately near-identical variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) or have overlapping routing/query purposes (deep_research, validate_claim, discover_tools, suggest_questions). The Polymarket cluster also has five tools that all surface 'edges' or 'arbitrage' with only subtle differences. Only the three GeoNet tools and the memory trio are cleanly distinct.

Naming Consistency3/5

The dominant style is snake_case, and clusters like ask_pipeworx_* and polymarket_* are internally consistent. However, verb/noun patterns vary widely across the set: some tools begin with verbs (get_quake, scan_dependency, generate_llms_txt), some are noun phrases (entity_profile, volcano_alerts, recent_changes), and some are plain nouns (polymarket_arbitrage). Readable but not a single predictable convention.

Tool Count2/5

34 tools is well above the 'heavy' threshold, and the server is named 'Geonet Nz' while only 3 of its 34 tools relate to GeoNet. The overwhelming majority are Pipeworx/data/prediction-market tools, making the server's scope massively broader than its name implies. The count itself is not unreasonable for the actual feature sprawl, but it is inappropriate for the apparent purpose.

Completeness4/5

Taking the real scope as 'general authoritative data research + memory + subscriptions + a little GeoNet', the surface is quite complete: query entry points, grounded verification, deep research, entity resolution, comparisons, claim validation, monitoring subscriptions, memory persistence, and feedback are all present. The GeoNet-specific subset is also adequate (get one, list recent, volcano alerts). Minor gaps exist, like no general GeoNet station/well data or subscription editing, but nothing causes dead ends.

Resources