Skip to main content
Glama

Tax Regulations

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.6/5.0
Behavior1/5

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

The annotations mark the tool as readOnlyHint:true, but the description explicitly states that setting mark_read:true "flag[s] returned events read so the next call only shows newer ones." This is a state-changing operation that contradicts the readOnlyHint annotation. Per rubric, any contradiction forces a score of 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 four sentences, front-loaded with the core action, and each sentence adds value: return fields, filtering, mark_read side effect, and polling/alternative access. 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?

With no output schema, the description helpfully specifies return fields (source, citation_uri, raw event payload). It covers the main behaviors and parameter interactions. The mark_read contradiction slightly undermines completeness, but the description itself is thorough enough for this simple read tool.

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?

The input schema has 100% description coverage for all five parameters. The description adds some reinforcement (e.g., filter by type with example "sec_8k", since as ISO timestamp, mark_read behavior) but does not meaningfully expand beyond the schema. Baseline of 3 is appropriate.

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 opens with a specific verb and resource: "Pull fired events from your subscription feed." It clearly defines the tool's scope (alerts written by the evaluator) and distinguishes it from related tools like recent_changes or list_subscriptions by focusing on the subscription feed's event stream.

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 clear context on when to use the tool (pulling fired alerts) and even offers a polling pattern and an alternative HTTP endpoint for scripts/dashboards. It does not explicitly exclude sibling tools, but the context is sufficient to infer appropriate use.

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

All Tax Regulations 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.5/5.0
Disambiguation2/5

Many tools overlap in purpose: ask_pipeworx and ask_pipeworx_beta are identical, while ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve as query/entry-point tools. The two tax-specific tools are distinct, but the sheer number of generic data-access tools makes it difficult for an agent to select the right one.

Naming Consistency2/5

Naming is a mix of snake_case (ask_pipeworx, tax_search), camelCase (ask_pipeworx_beta, compare_entities, discover_tools), and inconsistent verb styles (resolve_entity vs entity_profile vs scan_competitor_ai_presence). No clear pattern is discernible.

Tool Count1/5

The server is named 'Tax Regulations' but only 2 of 33 tools are tax-related. The other 31 tools are unrelated Pipeworx data-access, memory, subscription, and Polymarket tools, making the count wildly excessive and mismatched with the apparent purpose.

Completeness3/5

For the tax regulation domain, tax_search and tax_regulation cover keyword discovery and full-text retrieval, which is a functional core. However, the set lacks any other tax-specific operations (e.g., updates, comparisons, planning), and the majority of the tool surface is irrelevant to the stated server purpose, leaving notable gaps for an agent expecting a coherent tax toolset.

Resources