Skip to main content
Glama

Opentopography

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.4/5.0
Behavior4/5

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

Adds persistence details beyond annotations: authenticated users get persistent memory, anonymous sessions retain for 24 hours. No contradiction with 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 sentences, front-loaded purpose, no unnecessary 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?

Adequate for a simple storage tool; could mention return behavior but not required given simplicity.

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 coverage 100%; description adds example key patterns but no additional semantic detail beyond 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?

Clear verb 'Save' with explicit resource 'data the agent will need to reuse later'. Distinct from siblings recall 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 Guidelines5/5

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

Explicitly states when to use ('when you discover something worth carrying forward') and pairs with recall/forget for retrieval/deletion.

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

All Opentopography 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

B3.4/5.0
Disambiguation2/5

The tool set has several near-duplicate entries (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded; five polymarket_* tools), and the server name implies topography while most tools serve unrelated data lookups, making it hard to select the right tool for a task.

Naming Consistency3/5

Most tool names use snake_case and a verb-first style, but there are notable exceptions like 'datasets', 'dem', and 'forget', and the 'pipeworx' prefix is applied inconsistently (pipeworx_feedback, pipeworx_trending vs. ask_pipeworx). The pattern is readable but not fully uniform.

Tool Count2/5

With 34 tools, the count is excessive for a server named Opentopography, especially since only 3 tools (datasets, dem, point_elevation) relate to the implied domain. The bulk of tools belong to a general-purpose data and prediction-market service, creating a severe scope mismatch.

Completeness2/5

For the implied topography domain, the surface is severely incomplete: only dataset listing, a raster fetch, and a point elevation lookup are present, missing expected operations like elevation profiles, point cloud access, or data processing. For the broader Pipeworx domain, coverage is broad but this does not match the server's stated focus.

Resources