Skip to main content
Glama

Wynncraft

by io.github.pipeworx-io

Compare Entities

compare_entities
Read-onlyIdempotent

"Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing entities. type="company" pulls LATEST 10-K revenue + net income + cash + long-term debt from SEC EDGAR/XBRL (off-calendar fiscal years handled correctly — AAPL Sep, NVDA Jan, etc.). type="drug" pulls FAERS adverse-event counts, FDA approval counts, active trial counts. Results sorted by primary metric so "largest" / "most" / "biggest" reads off the top of the response. Returns paired data + pipeworx:// citation URIs per entity. Replaces 8–15 sequential lookups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type: "company" or "drug".
valuesYesFor company: 2–5 tickers/CIKs (e.g., ["AAPL","MSFT"]). For drug: 2–5 names (e.g., ["ozempic","mounjaro"]).

Schema Changelog

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

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent behavior. Description adds data sources (SEC EDGAR, FAERS), handling of off-calendar fiscal years, and output format (paired data + citation URIs). 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?

Front-loaded with common query patterns, then specifics. Each sentence adds value; no redundancy.

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?

No output schema, but description explains return format (paired data + URIs) and sorting. Covers all necessary context for a comparison tool.

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% and description adds meaning: explains what each type retrieves, gives examples of values, and clarifies min/max items.

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?

Description begins with concrete user intents and explicitly states 'side-by-side comparison of 2–5 companies or drugs in ONE parallel call.', clearly defining the tool's purpose and differentiating it from sequential lookups.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance: 'ALWAYS PREFER over sequential single-pack lookups when comparing entities.' Also notes efficiency gains by replacing 8–15 sequential calls.

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

All Wynncraft 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

B3.1/5.0
Disambiguation2/5

The set is split between Wynncraft game data tools and a large Pipeworx data cluster, and within the Pipeworx cluster there is heavy overlap: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical (the beta is currently identical), ai_visibility_check and scan_competitor_ai_presence do essentially the same thing at different granularities, and six polymarket_* tools cover overlapping prediction-market functionality. An agent would frequently struggle to choose the right tool.

Naming Consistency3/5

Snake_case with a mostly verb_noun pattern dominates (ask_pipeworx, compare_entities, resolve_entity, validate_claim), and families like polymarket_* and pipeworx_* are internally consistent. However, there is a notable mix of noun-only tools (guild, item_database, leaderboard, player, news) and the server is named Wynncraft while the majority of tools are Pipeworx-branded, which breaks overall coherence.

Tool Count2/5

40 tools is well beyond the borderline range, and the count is inflated by redundancy: multiple ask_pipeworx variants, several overlapping polymarket tools, a memory trio, and subscription management that arguably belong to a separate server. The Wynncraft portion alone would be nicely scoped (~9 tools), but the merged surface feels heavy and unfocused.

Completeness4/5

The Wynncraft side offers solid read coverage of players, guilds, items, leaderboards, news, and online status, which is appropriate for the domain. The Pipeworx side covers lookup, grounded verification, comparison, research, prediction markets, subscriptions, memory, and feedback, leaving few obvious dead ends for the stated meta-purposes.

Resources