Skip to main content
Glama

Oran Analiz Bot

Gerçekleşen istatistikler

realized_stats
Read-only

Oynanmış ya da oynanan bir maçın gerçekleşen istatistikleri (uygulamadaki gibi): üretilen xG, şut, isabetli şut, kaçan büyük fırsat, topla oynama, ceza sahasında topla buluşma, korner, kart; ilk yarı ayrımı ve goller. Oranların beklediğiyle maçın gerçekte nasıl oynandığını karşılaştırmak için.

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": {
      "matchKey": "<matchKey>"
    },
    "name": "realized_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
matchKeyYeslist_matches'ten alınan matchKey.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 the safety profile is covered. The description adds genuinely useful context beyond that: the data only exists for matches already played or in progress, and it includes a first-half breakdown — a real constraint an agent needs. It does not say what happens when the match has not started or the matchKey is unknown.

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?

Two sentences: the first front-loads the resource and its full content list, the second gives the motivating use case. The enumeration is long but each item earns its place by describing return values in the absence of an output schema; no filler wording.

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?

For a single-parameter read tool with annotations and no output schema, the description is nearly complete: it compensates for the missing output schema by enumerating the returned metrics and notes the played/in-play precondition. Only the failure behavior for unplayed matches or invalid keys is left unstated.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains that matchKey comes from list_matches and must match a 16-hex pattern. The description adds nothing about the parameter, which is acceptable given full schema coverage, so the 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 specific resource (realized/match statistics of a played or in-play match) and enumerates its contents (xG, shots, shots on target, big chances missed, possession, box touches, corners, cards, first-half split, goals). It implicitly separates itself from league-level siblings like league_stats, but never explicitly distinguishes itself from match_detail or match_odds, which could plausibly overlap.

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?

Usage is stated clearly: use it to compare what the odds expected with how the match was actually played, and it is scoped to matches that have been played or are in progress. There are no explicit exclusions or named alternatives (e.g. 'for pre-match expectations use match_odds'), so a small inference gap remains.

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