Skip to main content
Glama

Scryfall

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already cover readOnly, idempotent, destructive hints. Description adds context about scoping and pairing with remember/forget, but does not contradict 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?

Two sentences, front-loaded with core action, 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?

Completely covers usage, behavior, and relationships for a simple 1-param tool with no output schema.

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%. Description clarifies that omitting key lists all keys, adding meaning beyond 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?

States it retrieves a value saved via remember or lists all keys if key is omitted. Clearly distinguishes from siblings (remember, forget).

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 concrete use cases (target ticker, address, research notes) and scoping context. Lacks explicit when-not-to-use but implicit through examples.

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