Skip to main content
Glama

Oran Analiz Bot

Lig İstatistikleri

league_stats
Read-only

Uygulamadaki 'Lig İstatistikleri': bir ligin sezon maçları (skorlarıyla) ve sezon istatistikleri (maç sonucu, ilk yarı, alt/üst, karşılıklı gol vb. dağılımlar). Ligi adıyla ara; aynı adda birden çok lig varsa (ör. Süper Lig: Türkiye, Danimarka ...) ülke ver. Sezon adı (ör. 2025/2026) ve hafta verilebilir; geçerli sezonlar yanıtta.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "league": "<league>"
    },
    "name": "league_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekNoYalnız bu hafta.
leagueYesLig adı (ör. 'Trendyol Süper Lig', 'Premier Lig').
seasonNoSezon adı (ör. 2025/2026); varsayılan güncel sezon.
countryNoÜlke (aynı adlı ligleri ayırmak için).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real context on top: it discloses what the response contains (season fixtures with scores plus distribution breakdowns) and that valid season identifiers are returned in the response, which helps the agent self-correct on season input. It stops short of stating behavior on unknown league names, result size, or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: what the data is, how to disambiguate, and which optional filters exist. The content is front-loaded and every clause carries information, with only slight redundancy in the opening restatement of the app's own feature name.

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?

With no output schema and no nested parameters, the description carries the return-value burden and does so adequately by describing both fixture scores and aggregate distributions plus the returned valid seasons. Missing only edge-case behavior (invalid league name, empty results) for a lookup tool of this simplicity.

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%, so the schema already explains all four parameters, including the country disambiguation and the current-season default. The description reinforces the country-for-ambiguity rule and clarifies that week narrows to a single matchweek, but adds no format or syntax detail beyond the schema — baseline 3 applies.

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 names a concrete resource (a league's season matches with scores) and enumerates the statistic families returned (match result, first half, over/under, both-teams-to-score distributions), which goes well beyond restating the name. It does not, however, contrast itself with siblings such as realized_stats or similar_matches, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

It gives useful invocation guidance — look up by league name and supply country only when multiple leagues share a name (the Süper Lig Türkiye/Denmark example) — but this is parameter-level advice, not when-to-use guidance. There is no statement of when to prefer this tool over the statistics-oriented siblings, so usage is implied rather than directed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources