Skip to main content
Glama

Fmi

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

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds valuable context by disclosing the mark_read side effect that affects subsequent calls, the return payload shape, and the availability of the same feed via a separate endpoint. No contradiction with annotations.

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 concise (three sentences) yet covers purpose, return contents, filtering, mark_read behavior, and alternative access. It is front-loaded with the core purpose and every sentence carries information, with no 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?

For a tool with 5 parameters and no output schema, the description adequately explains what the tool returns, how to filter, the read-tracking behavior, and alternative access. The schema covers the remaining parameter details, making the description sufficiently complete for an agent.

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 each parameter is already described. The description augments this by providing a concrete type example ('sec_8k'), clarifying 'since' as an ISO timestamp, and explaining the practical effect of mark_read on future calls. This adds meaning beyond the schema.

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 tool's function with a specific verb ('Pull fired events from your subscription feed') and identifies the unique resource (alerts in the persisted feed). It distinguishes from siblings by specifying 'alerts' and detailing the return payload (source, citation_uri, raw event payload).

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 for when to use the tool (to retrieve fired alerts from the subscription feed) and notes that polling works fine. It mentions an alternative access method via a GET URL for scripts/dashboards, which is helpful, but it does not explicitly compare to sibling tools or state exclusions.

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

All Fmi 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.9/5.0
Disambiguation4/5

Most tools are well-differentiated, with detailed descriptions clarifying their distinct purposes. However, there is some overlap between the multiple 'ask' tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, suggest_questions) and between weather tools (forecast, latest_observations, recent_observations, warnings), which could cause confusion. Overall, ambiguity is low.

Naming Consistency5/5

All 34 tool names follow a consistent lowercase_with_underscores (snake_case) pattern. Names are descriptive and predictable, such as 'ask_pipeworx', 'entity_profile', 'polymarket_arbitrage', etc. No mixing of conventions like camelCase or inconsistent verb styles.

Tool Count3/5

The server has 34 tools, which is on the higher side given its broad scope covering weather, company research, prediction markets, and general data queries. While not excessive, it could be split into more focused servers for clarity. The count feels a bit heavy but still manageable.

Completeness4/5

The tool set covers a wide range of data domains (weather, company financials, prediction markets, news, memory, subscriptions) with reasonable completeness. Minor gaps exist, such as limited weather coverage (Finland only) and no direct support for non-company entities or unofficial data sources, but core workflows are well-supported.

Resources