Skip to main content
Glama

sportiq-mcp

by io.github.Ninjabeam20

cricket_player_matchup

Read-onlyIdempotent

Analyse the head-to-head matchup between two cricket players based on role and career stats.

Args: player_a: Player ID or name for the first player. player_b: Player ID or name for the second player.

Returns: data: {matchup_type, edge_holder, edge_reason, signals, role_a, role_b}. meta.estimated: true — heuristic model, not ball-by-ball H2H data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
player_aYesPlayer ID or name for the first player.
player_bYesPlayer ID or name for the second player.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
metaNo
errorNo

Schema Changelog

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

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description openly discloses that this is a heuristic model, not ball-by-ball H2H data, and clarifies that results are estimated (meta.estimated: true). It also reveals the return shape including edge_holder and edge_reason, adding meaningful behavioral context.

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 compact, well-organized with Args and Returns sections, and contains no filler. The core purpose is front-loaded and the heuristic caveat is clearly stated, earning its place.

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 two-parameter read-only tool with a documented output schema, the description is complete. It covers the purpose, input semantics, return fields, and the critical estimation limitation, leaving no meaningful gap for an agent to invoke it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, and the description repeats the schema's player_a/player_b semantics without adding extra detail. There is no additional guidance on ID formats, name resolution behavior, or input preprocessing, so it adds no value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool analyzes the head-to-head matchup between two cricket players based on role and career stats, with a specific verb and resource. However, it does not explicitly differentiate this from the sibling tool cricket_head_to_head, leaving some ambiguity.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives like cricket_head_to_head or cricket_player_form_index. The description implies pairwise player comparison but does not specify exclusions, routing conditions, or preferred scenarios.

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

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

Sport prefixes make the three domains easy to separate, and most tools have clear purposes. However, several tools overlap: football_match_predictor vs football_xg_model, f1_head_to_head_pace vs f1_race_pace_compare, and the cricket fantasy tools (build_dream11, captain_recommendation, differential_picks) all require careful reading to avoid misselection.

Naming Consistency4/5

The sport prefix + snake_case pattern is consistent and retrieval tools uniformly use get_, which creates predictability. The main deviation is that many analysis/model tools are noun phrases rather than verb_noun (cricket_head_to_head, football_knockout_path, f1_tyre_degradation), but they remain readable and scoped.

Tool Count2/5

44 tools is well above the 25+ threshold for a single server and will strain agent context and tool-selection quality. Each sport block is individually reasonable at 13-15 tools, but combining three sports plus cross-sport and health utilities makes the overall surface too large.

Completeness3/5

Core workflows are broadly covered: live data, schedule/standings, match prediction, tournament simulation, fantasy help, and strategy analysis exist for each sport. However, there are notable dead ends: cricket_player_form_index needs a player_id no exposed tool returns, football_get_match_stats requires an API-Football numeric ID not mapped anywhere, and f1_get_lap_times references a stints endpoint that is not exposed as a tool.

Resources