Skip to main content
Glama

Oran Analiz Bot

Maç detayı

match_detail
Read-only

Maçın uygulamadaki detay sayfası: iki takımın son formu (seri, attığı/yediği gol, 2,5 üst, karşılıklı gol), aralarındaki maçların özeti (H2H), puan durumu, hakem ve kart ortalamaları, takım istatistikleri (korner, kart; iç saha/deplasman), hava durumu; bitmiş maçta olaylar (goller, kartlar). Analizden önce maçı tanımak için 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_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
matchKeyYeslist_matches'ten alınan matchKey.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 value by noting that event data (goals, cards) only appears for finished matches, which is a genuine conditional behavior. Beyond that it does not state data freshness, whether sections can be missing, or how large the payload is.

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 opening clause, followed by a dense but scannable content inventory and a closing usage instruction. The long semicolon-separated inventory is efficient, though the list of content categories is on the edge of being overly packed.

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 correctly carries the burden of describing return content and does so thoroughly across form, H2H, standings, referee, stats, weather, and events. It is nearly complete for a read-only aggregator, missing only caveats about data availability or payload structure.

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 single matchKey parameter is already documented as coming from list_matches, so the baseline is 3. The description itself says nothing about the parameter, adding no meaning 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?

Opens with a specific resource ('Maçın uygulamadaki detay sayfası') and then enumerates exactly what the page contains: form, H2H, standings, referee/card averages, team stats, weather, and finished-match events. An agent knows this is the aggregate match-detail reader. It loses a point for not distinguishing itself from narrower siblings like match_referee or match_lineup, whose data it also claims to include.

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?

'Analizden önce maçı tanımak için kullan' gives a clear situational trigger: call this first to get oriented before deeper analysis. There are no explicit exclusions or named alternatives for the overlapping referee/lineup data, so it is clear context without routing rules.

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