Skip to main content
Glama

Opentopography

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

TDQS

A3.8/5.0
Behavior1/5

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

Annotations indicate readOnlyHint=true (no write operations), yet the description states that setting mark_read:true flags events as read, which is a state change. This contradicts the readOnlyHint annotation, so score is 1.

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 concise (about 100 words), front-loaded with the core purpose, and each sentence adds necessary context without redundancy.

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?

For a tool with 5 optional parameters and no output schema, the description covers usage scenarios, behavior of mark_read, and an alternative access method. However, the annotation contradiction undermines overall completeness.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the effect of mark_read and providing an example for type filtering, but does not add details for all parameters.

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 pulls fired events from a subscription feed, and it specifies the returned fields (source, citation_uri, raw payload). It distinguishes itself from siblings by focusing on alert retrieval with specific filtering options.

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 notes that polls work fine and provides an alternative REST endpoint for scripts/dashboards. It also explains that setting mark_read:true affects subsequent calls. However, it does not explicitly state when not to use this tool versus others.

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