Skip to main content
Glama

Scryfall

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

A4.7/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false. The description adds value by explaining the mark_read parameter's effect on read state and that polling is safe. 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 a single paragraph of ~5 sentences, front-loaded with the core purpose, then detailing parameters and alternative access. Every sentence adds value with no redundancy or fluff.

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?

Given 5 parameters all described in schema, and no output schema, the description provides sufficient context by listing what each event carries (source, citation_uri, raw payload). It also mentions the direct endpoint for alternative use. Could be slightly more complete by noting default ordering or pagination, but it's adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (all 5 parameters have descriptions). The description enhances each parameter: gives an example for 'type' (sec_8k), specifies ISO timestamp for 'since', explains the effect of 'mark_read' and 'unread_only', and mentions 'limit' implicitly through the default. 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 starts with 'Pull fired events from your subscription feed' — a clear verb+resource statement. It specifies what each event carries (source, citation_uri, raw payload) and lists filtering options. This distinguishes it from sibling tools like list_subscriptions or subscribe which manage subscriptions rather than retrieve events.

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 explains when to use this tool ('Polls work fine') and the alternative direct endpoint ('the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards'). It describes filtering options but doesn't explicitly state when not to use it or compare to specific siblings.

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

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

Most tools have distinct purposes, but the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) plus deep_research creates real boundary confusion, and the six polymarket_* tools overlap enough to require careful reading. The few Scryfall card tools are clearly distinct from the Pipeworx bulk, but the name mismatch adds selection friction.

Naming Consistency4/5

All tool names use snake_case and most follow a verb_noun pattern (get_card, search_cards, resolve_entity, validate_claim). There are deviations like entity_profile, deep_research, and pipeworx_trending, but the nested families (ask_pipeworx*, polymarket_*) are internally consistent and predictable.

Tool Count2/5

35 tools is above the 25+ threshold and is especially mismatched with the server name 'Scryfall', which implies a focused MTG card server. Only 4 of 35 tools relate to Scryfall; the remaining 31 form a sprawling data-research platform that would be more appropriately split into separate servers.

Completeness4/5

The dominant Pipeworx data-research surface is remarkably complete: universal lookup, grounded answers, deep research, entity profiles, comparisons, entity resolution, claim validation, change feeds, subscriptions, memory, and discovery. The Scryfall subset covers core card lookup (search, get by name, random, list sets) but lacks rulings, set details, and card-by-ID lookups, which is a minor gap relative to the server's stated name.

Resources