Skip to main content
Glama

The Undesirables TCG Oracle

by io.github.sailorpepe

souls_in_wallet

Show every Undesirable soul a wallet holds, with each soul's public prediction track record and its most recent calls. FREE — no payment, no signature, no wallet connection required.

Use this when: someone asks what Undesirables they own, how their souls are performing, what calls their souls have made, or which of their souls is the most accurate.

HOW IT WORKS • Ownership is read from Ethereum mainnet (ERC-721 0xA893648A701C03B14bF2FB767B72b2C55ed5c17A). Only the minted souls 1-273 have public records. • Nothing here is private, so you can look up ANY address — the caller does not have to prove they own it. Ask the user for their address. • Each minted soul locks 3 card predictions weekly, chosen deterministically from its on-chain personality traits. The oracle scores them 30 days later against real market prices.

WHAT YOU GET BACK • souls[] — per soul: rating (A+..F / UNRATED), matured, hits, hit_rate, brier, open_calls, and recent_calls with each call's outcome (hit / miss / push) • wallet_totals — combined open + matured calls and overall hit rate • best_soul — the holder's most accurate soul, once any have matured

HOLDERS WITH SEVERAL SOULS: this is a roster. Offer to compare them, or to speak as a specific one — each has different traits and its own record.

IMPORTANT — ratings mature on a schedule. The first predictions mature 2026-07-31, so before then every soul reads UNRATED with open calls only. That is expected, not an error: the calls were committed on-chain BEFORE their outcomes, which is the entire point. Say so rather than implying the soul has no history.

Args: address: 0x-prefixed EVM address to look up. calls: recent scored calls to include per soul (0-12, default 5).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
callsNo
addressYes

Schema Changelog

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

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden, and it excels: it discloses the Ethereum mainnet source contract, the minted-IDs range, that any address can be queried without ownership proof, the deterministic prediction mechanism, the 30-day oracle scoring delay, and the UNRATED schedule with the exact maturity date.

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 long but well structured into labeled sections, with the core purpose and usage front-loaded. Every section earns its place: input semantics, behavior, return fields, edge-case expectations, and user-handling guidance all add value that would otherwise be absent.

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?

The tool has no output schema, so the description's explicit enumeration of souls[], wallet_totals, and best_soul is essential and complete. It also covers the expected UNRATED-before-2026-07-31 edge case and instructs the agent how to frame it, leaving no critical gap for correct invocation.

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 description coverage is 0%, but the description fully compensates by defining address as a 0x-prefixed EVM address and calls as recent scored calls per soul with a 0-12 range and default 5. It also adds practical guidance to ask the user for their address because no wallet connection is required.

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 opens with a specific verb and resource: 'Show every Undesirable soul a wallet holds,' and then details the per-soul track record and recent calls. It clearly frames this as a wallet roster, distinguishing it from single-soul or scoring-focused sibling tools.

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 gives explicit 'Use this when' triggers: ownership questions, performance checks, recent call queries, and most-accurate-soul comparisons. It does not explicitly name alternatives or state when not to use this tool, though the triggers are clear enough for selection.

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

All The Undesirables TCG Oracle 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.6/5.0
Disambiguation2/5

Multiple tools have unclear boundaries: card_forecast and simulate_price both return conformal-calibrated forecasts with Safe-Hold/Momentum grades; grade_card and grade_or_not both include ROI verdicts; check_accuracy and oracle_scorecard are both accuracy dashboards; market_snapshot and trending_cards both surface market movers. The descriptions carry some differentiators, but an agent would frequently misselect among these pairs.

Naming Consistency3/5

All names are snake_case, which is consistent, but the verb/noun pattern is mixed: some are verb_noun (check_accuracy, grade_card, optimize_portfolio, search_tcg_products, simulate_price), while many are noun_noun or noun phrases (card_forecast, market_snapshot, oracle_scorecard, sports_board, souls_in_wallet). The result is readable but not predictable.

Tool Count3/5

23 tools sits in the heavy 16–25 band, and the server spans several domains: TCG pricing/forecasting/grading, souls and fantasy, the Syndicate game, and technocore. It is not extreme, but the count feels bigger than a single focused oracle needs.

Completeness4/5

The core card-market workflow is well covered: search, price forecast, simulation, trending, market snapshot, grading, ROI, loan preview, and accuracy verification are all present. Minor gaps include the paid loan quote for off-board cards not being exposed as an MCP tool and some redundancy between card_forecast and simulate_price, but no CRUD lidecycle is required for a read-only oracle.

Resources