Skip to main content
Glama

Geonet Nz

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint=true and idempotentHint=true. The description adds that the tool returns top-N relevant tools with full schemas and curated examples, ready to call directly, which is valuable 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph that efficiently covers purpose, usage, and output without redundancy. It is front-loaded with the most critical information.

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?

Given the complexity (6 parameters, no output schema), the description fully covers what the tool does, when to use it, what it returns, and how to construct queries. It leaves no critical 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 description coverage is 100%, so baseline is 3. The description adds minimal additional meaning beyond the schema's parameter descriptions, mainly reinforcing the query parameter's role.

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 the verb 'find' and resource 'tools', and explicitly lists the domains. It distinguishes from siblings by positioning itself as the tool discovery mechanism.

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?

The description explicitly says 'Call this FIRST when you have many tools available', providing clear when-to-use and implied when-not-to guidelines.

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