Skip to main content
Glama

Geoapify

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

A4.2/5.0
Behavior4/5

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

The description adds behavioral context beyond annotations: it explains that mark_read flags events as read, affecting future calls, and describes the return contents. Annotations already indicate read-only, idempotent, and non-destructive behavior, which the description aligns with.

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 cover purpose, content, and key behavior without fluff. Information is front-loaded: first sentence states the action and resource, second describes what is returned, third explains filtering and mark_read. Every sentence adds value.

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 5 parameters with full schema descriptions and no output schema, the description covers the main return fields, filtering options, and mark_read behavior. It does not mention limit defaults or unread_only explicitly, but schema covers those. Provides alternative access method, enhancing completeness.

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 is 100%, so baseline is 3. The description adds examples for type ('sec_8k') and since (ISO timestamp), and explains mark_read's effect. However, it does not mention limit or unread_only, which are described in the schema. Some added value but not complete.

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 'Pull' and the resource 'fired events from your subscription feed', distinguishing it from sibling tools like list_subscriptions or subscribe. It specifies the content of the return (source, citation_uri, payload) and 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 provides context for usage, such as filtering by type and since, and explains the mark_read feature. It also mentions that polling works fine and points to an alternative access method for scripts/dashboards. However, it does not explicitly compare to other tools or state when not to use it.

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

All Geoapify 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.8/5.0
Disambiguation2/5

Multiple tools have overlapping purposes, such as ask_pipeworx, ask_pipeworx_grounded, entity_profile, compare_entities, and validate_claim, all retrieving entity data. Agents may struggle to choose correctly between them. Likewise, bet_research, polymarket_edges, and polymarket_arbitrage cover similar prediction market territory.

Naming Consistency3/5

All tool names use underscores, but the verb/noun order varies: compare_entities (verb_noun), entity_profile (noun_noun), scan_competitor_ai_presence (verb_noun), bet_research (noun_verb). Some names are overly long (scan_competitor_ai_presence). The pattern is readable but not fully consistent.

Tool Count3/5

With 31 tools, the count is high but not extreme. However, the set covers geospatial, data retrieval, prediction markets, npm scanning, and memory/feedback - too broad for a single server. Many tools feel added without clear justification, making the set feel bloated.

Completeness2/5

The geospatial subset is incomplete (missing elevation, distance matrix, isochrones). The data access tools overlap rather than form a complete API surface (e.g., no entity update/delete). Prediction market tools are numerous but redundant. The server tries to do too much and lacks depth in any area.

Resources