Skip to main content
Glama

Oran Analiz Bot

Kadro

match_lineup
Read-only

Uygulamadaki Kadro sekmesi: muhtemel ya da kesin kadrolar (diziliş, ilk 11, yedekler, eksikler, kart sınırındakiler), oyuncu sezon istatistikleri, Kadro Gücü (her oyuncunun piyasa değeri ve takımın ilk 11 / tüm kadro toplamı, euro) ve teknik direktörlerin takımdaki dönem performansı. Kaynak geçici olarak yanıt vermezse not_found dönebilir.

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_lineup"
  }
}

Input Schema

NameRequiredDescriptionDefault
matchKeyYeslist_matches'ten alınan matchKey.

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 the safety profile is covered. The description adds a genuine behavioral detail beyond that: the source may temporarily be unavailable and the tool can return not_found, which tells the agent to handle a soft-failure case. It does not describe response shape or completeness of the data, keeping it below a 5.

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?

The definition is front-loaded with the resource name and packs the content inventory into one dense sentence, followed by a short failure-mode note. It is efficient, though the long enumeration is somewhat list-like and could be grouped more crisply.

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 telling the agent what comes back, and it does so by enumerating lineups, stats, squad value, and coach performance. Combined with the not_found caveat, an agent has enough to call it correctly; only the exact response structure remains unspecified.

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 required parameter with 100% schema description coverage, and the schema already states that matchKey comes from list_matches with a hex pattern. The description adds no further meaning about the parameter, 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 (the 'Kadro' tab) and enumerates its contents: probable/confirmed lineups with formation, first XI, substitutes, absences, card-limit players, player season stats, Squad Power in euros, and coach tenure performance. An agent knows exactly what data domain this covers, though it never contrasts itself with siblings like match_detail, which likely also returns match-level data.

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?

Usage is only implied: an agent infers it should call this when it needs lineup, squad-value, or coach-tenure data for a given match. There is no explicit when-to-use/when-not-to-use statement and no named alternative for overlapping needs such as match_detail.

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