Skip to main content
Glama

Oran Analiz Bot

find fixtures by form

find_fixtures_by_form
Read-only

Yaklaşan maçları takımların form şartına göre tarar: üst üste galibiyet/mağlubiyet, son N maçta galibiyet sayısı, WDL deseni. Bir sonucu diğer araçlarla açmak için matchKey'ini list_matches'ten (tarih + takım adı) al.

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": {
      "dates": "<dates>",
      "minConsecutiveWins": "<minConsecutiveWins>",
      "minConsecutiveLosses": "<minConsecutiveLosses>",
      "minWins": "<minWins>",
      "inLast": "<inLast>",
      "formPattern": "<formPattern>",
      "league": "<league>",
      "limit": "<limit>"
    },
    "name": "find_fixtures_by_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
datesYesArray of YYYY-MM-DD dates to scan. E.g. ['2026-03-28','2026-03-29'] for today and tomorrow.
limitYesMax fixtures to return. Default 30.
inLastYesWindow size for minWins check. Default: 5.
leagueYesOptional league/country filter to narrow scan (partial match).
minWinsYesMinimum wins within last N matches (use with inLast). E.g. minWins:4, inLast:5 = at least 4 wins in last 5.
formPatternYesExact form string to match from most recent (W/D/L). E.g. 'WWWWW' = 5 consecutive wins, 'WDWWW' = specific pattern.
minConsecutiveWinsYesMinimum consecutive wins from most recent match. E.g. 5 = last 5 all wins.
minConsecutiveLossesYesMinimum consecutive losses from most recent match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover safety (readOnlyHint true, openWorldHint false), so the bar is lower. The description adds one genuinely useful behavioral fact — that matchKey is not returned here and must be obtained from list_matches — but says nothing about result ordering, output shape, or what happens when no fixtures satisfy all the criteria.

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, front-loaded with the filtering conditions followed by the cross-tool follow-up instruction; nothing is wasted. Mixing Turkish prose with an English tool name and schema is not a verbosity problem but slightly reduces scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 required parameters and no output schema, the definition should clarify more. Most notably it never states whether the criteria are ANDed together (formPattern vs minConsecutiveWins vs minWins are all required) or what a result row contains, leaving a real ambiguity for a tool of this complexity.

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 each parameter is documented with an example (e.g. minWins:4, inLast:5), so the schema already carries semantics. The description restates the same condition families without adding format or interaction details beyond the schema, which is the baseline-3 case.

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 uses a specific verb (”tarar” – scans) with a specific resource (”Yaklaşan maçları” – upcoming matches) and enumerates the form criteria it filters on (consecutive W/L, wins in last N, WDL pattern). It distinguishes itself from odds/goals-based siblings by the criteria it names, though it never names those siblings explicitly.

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?

Implicit guidance is present: the tool targets upcoming fixtures, and it tells the agent to obtain matchKey from list_matches in order to open a result with other tools. There is no explicit statement of when to prefer find_fixtures_by_goals_form, find_fixtures_by_odds, or find_fixtures_combined instead, and no exclusion 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