Skip to main content
Glama

Property Records

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).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A3.5/5.0
Behavior1/5

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

The annotation declares readOnlyHint=true, but the description discloses that setting mark_read=true flags events as read, which is a state-modifying side effect. This contradicts the read-only annotation, and per rubric, transparency must be scored 1 when a contradiction exists.

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 4 sentences, front-loaded with the main purpose, and includes only relevant details: filtering, mark_read, polling, and an alternative access method. 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?

Without an output schema, the description compensates by specifying the return payload (source, citation_uri, raw event). It covers filtering, mark_read persistence, and the polling/endpoint alternative. Minor gaps like the interaction between mark_read and unread_only remain, but overall it is thorough.

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?

The schema already documents all 5 parameters, but the description adds valuable context beyond schema: it explains the mark_read behavior in detail (affects future calls), provides an example filter value (sec_8k), and describes the response structure, enhancing understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool pulls fired events from the subscription feed, specifying the action and resource. It details the content of returned events (source, citation_uri, payload) and provides filtering examples, making its purpose distinct from siblings like 'recent_changes'.

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?

It explicitly notes that polling works fine and points to an alternative endpoint for scripts/dashboards, giving clear usage context. It doesn't list when to avoid this tool vs. siblings, but the guidance is sufficient for typical use.

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

All Property Records 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.6/5.0
Disambiguation2/5

Multiple tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical variants of the same router, and there are six polymarket-related tools with overlapping arb/edge/fill-risk purposes. Property-specific tools are distinct but buried among many unrelated meta-tools.

Naming Consistency3/5

All names use snake_case, but the structural pattern is inconsistent: some are verb_noun (ask_pipeworx, validate_claim), others noun_verb (property_lookup), and many are noun_noun (entity_profile, polymarket_arbitrage). No clear systematic convention across the set.

Tool Count2/5

33 tools is far too many for a server labeled 'Property Records'—only two tools (property_lookup, property_coverage) actually serve that purpose. The rest belong to unrelated domains (general data lookup, prediction markets, memory, subscriptions), making the surface feel bloated and unfocused.

Completeness2/5

For a property-records server, the surface is incomplete: it only provides lookup plus a coverage matrix, with no other property-related operations (e.g., tax history, comparable sales) and no way to handle unsupported jurisdictions beyond a simple flag. The unrelated tools do not contribute to the stated domain, leaving the core purpose thinly covered.

Resources