Skip to main content
Glama

Oran Analiz Bot

Hakem

match_referee
Read-only

Uygulamada hakeme tıklayınca açılan ekranın aynısı: maçın hakeminin yönettiği maçlar ve özetleri. Sarı/kırmızı kart ve penaltı toplam/ortalamaları, sonuç dağılımı (1/X/2), karşılıklı gol, 2,5 üst, 6+ gollü maçlar, İY/MS kombinasyon sayıları (1/1, 2/1 ...) ve lig bazında istatistik. Sezon, lig, yalnız bu maçın takımları ve aramayla daraltılır; liste ayrıca İY/MS kombinasyonu ya da 6+ gol ile süzülür. Analizde yalnız aynı hakemin maçları için analyze_odds / similar_matches'te filter.sameReferee kullan.

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": "match_referee"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDönecek maç sayısı (varsayılan 40, en yeni önce).
combosNoMaç listesini bu İY/MS sonuçlarıyla süz (maçın kendi ev/deplasman yönünde).
leagueNoYalnız bu lig (kısmi ad, ör. 'Süper Lig').
searchNoTakım ya da lig adında arama (kısmi).
seasonNoYalnız bu sezon (ör. 2026/2027); geçerli değerler yanıttaki `seasons` listesinde.
matchKeyYeslist_matches'ten alınan matchKey.
overSixOnlyNoMaç listesini yalnız 6 ve üzeri gollü maçlarla süz.
sameTeamsOnlyNoYalnız bu maçın iki takımından birinin oynadığı maçlar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 then adds real behavioral value: it enumerates what the response contains (card/penalty totals and averages, 1/X/2 distribution, BTTS, over 2.5, 6+ goal counts, HT/FT combination counts, league-level stats) and notes that the seasons list arrives in the response.

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?

Purpose is front-loaded in the first clause, followed by content inventory, filtering behavior, and cross-tool guidance in a logical order. The statistics enumeration is long but each item tells the agent what data to expect; minor redundancy between the filter sentence and the schema descriptions.

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, the description carries the burden of describing the return payload, and it does so thoroughly via the stat enumeration. Combined with annotations covering the read-only/closed-world profile and a fully documented schema, little an agent needs is missing.

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 coverage is 100%, so every parameter is already documented in the schema. The description groups the narrowing dimensions (season, league, same teams, search) and the list-level filters (HT/FT combo, 6+ goals) but adds no syntax or format detail beyond that, making the baseline 3 appropriate.

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?

Names a concrete verb+resource: it returns the matches refereed by the match's referee plus aggregate stats, and explicitly frames it as the in-app referee screen equivalent. This is unmistakably distinct from sibling tools like match_detail or league_stats.

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 last sentence routes the agent to the right alternative for deeper analysis: use filter.sameReferee inside analyze_odds / similar_matches when only same-referee matches matter. It does not state explicit exclusions (e.g. when to prefer match_detail's referee info instead), so it stops short of a full 5.

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