Skip to main content
Glama

dogsapi

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

TDQS

A3.7/5.0
Behavior1/5

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

Description states that setting mark_read:true flags returned events as read so the next call shows only newer ones, which is a state-mutating side effect. This directly contradicts the readOnlyHint:true annotation. The description also adds other useful context, but the contradiction forces a score of 1 per rubric.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is about four sentences, front-loaded with the core action. Each sentence carries useful information: return fields, filtering options, mutation flag, polling, and an alternative endpoint. It is dense but not bloated, and the structure flows logically from purpose to details to alternatives.

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 appropriately explains the return shape (source, citation_uri, raw payload). It also covers all five parameters, side effects, polling behavior, and an external access route. Minor deduction for the contradiction with readOnlyHint, which introduces ambiguity about whether the tool is always side-effect free.

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 covers 100% of parameters, so baseline is 3. The description adds value by giving a concrete type example ('sec_8k'), explaining that since is an ISO timestamp, and clarifying mark_read semantics (flagging events read so the next call only shows newer ones). These go beyond the schema's minimal descriptions.

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?

Description opens with the specific verb 'Pull fired events from your subscription feed' and names the resource (alerts feed). It clearly distinguishes itself from sibling tools like list_subscriptions by focusing on fired events and alert payloads, not subscription management. The return fields and filtering options further reinforce its purpose.

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?

Provides clear usage context: filter by type and/or since, mark_read behavior, polling is fine, and an alternative HTTP endpoint for scripts/dashboards. It does not explicitly name a when-not-to-use case or sibling alternative, but the guidance is sufficient for an agent to decide when to use this tool.

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

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

Several tools have genuinely unclear boundaries: ask_pipeworx and ask_pipeworx_beta are described as currently identical, ask_pipeworx_grounded shares the same router, and the polymarket_edges/arbitrage/fill_risk/bet_research group overlaps heavily in purpose. The remaining clusters (dog data, memory, subscriptions) are mostly distinct, so the confusion is concentrated in a few spots but severe there.

Naming Consistency3/5

Nearly all names are lower_snake_case and readable, but the conventions are mixed: get_/list_/ask_/scan_ verb-noun names sit alongside bare verbs (remember, forget, recall), noun-phrase names (entity_profile, bet_research, pipeworx_trending), and a versioned suffix (ask_pipeworx_beta). No single predictable pattern covers the whole set.

Tool Count2/5

At 35 tools, the server is well past the 25+ threshold for feeling bloated, and the count is dominated by unrelated Pipeworx, prediction-market, and AI-visibility tools rather than the dog-data domain implied by 'dogsapi'. Only four tools actually serve the dog API, making the surface both oversized and misaligned with the server name.

Completeness3/5

The broad data-access side is thorough, covering discovery, universal routing, grounded answers, deep research, entity profiles, comparisons, claim validation, memory, and subscriptions. However, the nominal dog domain is thin (list/get/groups/facts with no filtering or additional operations), subscriptions have no update path, and some one-off tools like generate_llms_txt and scan_dependency exist without any surrounding lifecycle.

Resources