Skip to main content
Glama

Oran Analiz Bot

Maç listesi

list_matches
Read-only

Bir günün futbol maçlarını uygulamadaki gibi listeler: lig, saat, ev/deplasman, durum (scheduled/live/finished), İY ve MS skoru. Her maçın matchKey'ini verir; maça özel diğer araçların hepsi matchKey ister, bu yüzden ilk adım budur. Geçmiş günler de çalışır (ör. 2025-08-30) ve ilk çağrı yavaş olabilir. Bir günde yüzlerce maç olabilir; aradığın belliyse search ile takım ya da lig adına göre daralt.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD. Varsayılan: bugün (İstanbul saati).
searchNoİsteğe bağlı takım ya da lig adı süzgeci (büyük/küçük harf duyarsız, kısmi).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses a latency caveat (the first call may be slow) and a volume warning (a single day may contain hundreds of matches), which directly shape how an agent should plan and filter. It also enumerates the returned fields and status values, so the agent knows the shape of the response despite no output schema.

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?

Front-loaded with what is returned, then the strategic point (matchKey is required downstream), then practical caveats (latency, volume, filtering). Every sentence carries information an agent needs; nothing is padded or repeated from the schema.

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 list tool with no output schema, the description covers return fields, the key value it emits, latency, result volume, historical date support, and narrowing strategy — everything needed to call it correctly and use the result.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not convey: that historical dates actually work, with a concrete example (2025-08-30), and that `search` is the recommended narrowing mechanism when the target is known. The date pattern's default behavior is left to the schema, which is fine.

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?

States a specific verb and resource (lists a day's football matches) plus exactly what comes back: league, time, home/away, status (scheduled/live/finished), half-time and full-time scores, and the matchKey. It also positions itself against siblings by declaring it is the mandatory first step because every other match-specific tool needs the matchKey.

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?

Gives clear context for when to call it (first step, any date including past dates) and how to narrow results with the `search` filter when the target is known. It stops short of explicit exclusions or naming the sibling tools an agent should switch to for other needs, but the entry-point framing removes most ambiguity.

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