Skip to main content
Glama

Ecos Kr

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/5.0
Behavior3/5

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

Annotations already provide readOnlyHint, idempotentHint, etc. The description adds that setting mark_read:true flags events as read, affecting subsequent calls. This adds context beyond annotations, but no mention of rate limits or other behavioral details.

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 a single paragraph of four sentences that front-loads the main purpose. Every sentence adds useful information with no redundancy or wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (read-only listing with filters) and comprehensive schema and annotations, the description is complete. It explains returned fields, filtering, the mark_read behavior, and provides an alternative access method.

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 providing an example for 'type' (e.g., 'sec_8k') and explaining the effect of 'mark_read' on future calls. This goes beyond the schema descriptions.

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 a subscription feed, specifying verb and resource. It does not explicitly distinguish from siblings like 'list_subscriptions' or 'recent_changes', but the specific resource and action are well-defined.

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 indicates that polling works fine and provides an alternative endpoint (GET registry.pipeworx.io/alerts.json) for scripts and dashboards. It mentions filtering options but lacks explicit when-not-to-use guidance relative to siblings.

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

All Ecos Kr 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
Disambiguation3/5

Several tool families overlap heavily: ask_pipeworx and ask_pipeworx_beta are functionally identical today, and the polymarket_edges/arbitrage/fill_risk/kalshi_spread family plus entity_profile/recent_changes/compare_entities cover adjacent jobs. The descriptions are detailed enough to separate them with careful reading, but an agent could easily select the wrong one without deep inspection.

Naming Consistency3/5

The set has recognizable prefixes like ecos_, ask_pipeworx, and polymarket_, but it also mixes verb_noun names (validate_claim, discover_tools), bare verbs (remember, forget, recall), reversed/gerund forms (bet_research, pipeworx_trending), and special tokens (generate_llms_txt). The naming is readable on a per-family basis but not predictable across the full surface.

Tool Count2/5

35 tools is above the comfortable range for a coherent tool set, and several entries are near-duplicates or wrappers: ask_pipeworx_beta is currently identical to ask_pipeworx, and scan_competitor_ai_presence wraps ai_visibility_check. The prediction-market and company-research families could be consolidated without losing capability.

Completeness4/5

For the server's broad scope, lifecycle coverage is strong: ECOS has search/items/get/indicators, subscriptions have create/list/read/cancel, memory has save/read/delete, and the data-research surface covers lookup, grounded verification, comparison, profiles, changes, and discovery. Minor gaps exist, such as no direct tool to fetch a pipeworx:// record by URI or execute a single catalog tool directly, but these are workable.

Resources