Skip to main content
Glama

Oran Analiz Bot

find fixtures by goals form

find_fixtures_by_goals_form
Read-only

Yaklaşan maçları takımların son maçlardaki gol istatistiklerine ya da İY/MS formuna göre tarar: attığı/yediği ortalama gol, karşılıklı gol oranı, gol yemediği maç oranı, İY/MS sürprizi. 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>",
      "inLast": "<inLast>",
      "side": "<side>",
      "minAvgGoalsScored": "<minAvgGoalsScored>",
      "maxAvgGoalsScored": "<maxAvgGoalsScored>",
      "minAvgGoalsConceded": "<minAvgGoalsConceded>",
      "maxAvgGoalsConceded": "<maxAvgGoalsConceded>",
      "minAvgTotalGoals": "<minAvgTotalGoals>",
      "maxAvgTotalGoals": "<maxAvgTotalGoals>",
      "minBttsRate": "<minBttsRate>",
      "minCleanSheetRate": "<minCleanSheetRate>",
      "minScoredInAll": "<minScoredInAll>",
      "maxFailedToScoreRate": "<maxFailedToScoreRate>",
      "minTotalGoalsScored": "<minTotalGoalsScored>",
      "maxTotalGoalsScored": "<maxTotalGoalsScored>",
      "minTotalGoalsConceded": "<minTotalGoalsConceded>",
      "maxTotalGoalsConceded": "<maxTotalGoalsConceded>",
      "minTotalGoals": "<minTotalGoals>",
      "maxTotalGoals": "<maxTotalGoals>",
      "minGoalsPerMatch": "<minGoalsPerMatch>",
      "minMatchesScoredAbove": "<minMatchesScoredAbove>",
      "minIymsSurpriseRate": "<minIymsSurpriseRate>",
      "maxIymsSurpriseRate": "<maxIymsSurpriseRate>",
      "league": "<league>",
      "limit": "<limit>"
    },
    "name": "find_fixtures_by_goals_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYesWhich team to check. Null = either.
datesYesYYYY-MM-DD dates to scan.
limitYesMax results. Default 30.
inLastYesHow many recent matches to look at. Default 5.
leagueYesOptional league/country filter.
minBttsRateYesFraction (0-1) of last N matches where BOTH teams scored.
maxTotalGoalsYesTotal scored+conceded combined must be at most N in last inLast matches.
minTotalGoalsYesTotal scored+conceded combined must be at least N in last inLast matches. E.g. minTotalGoals=10 for 'son 5 maçında toplam 10+ gol'.
minScoredInAllYesIf true, team must have scored in ALL last N matches.
maxAvgTotalGoalsYesTotal goals per match avg must be ≤ N.
minAvgTotalGoalsYesTotal goals per match avg must be ≥ N.
minGoalsPerMatchYesPer-match goal threshold for minMatchesScoredAbove. Default 2 if not set.
maxAvgGoalsScoredYesTeam must average at most N goals scored per match.
minAvgGoalsScoredYesTeam must average at least N goals scored per match.
minCleanSheetRateYesFraction (0-1) of last N matches where team kept a clean sheet.
maxAvgGoalsConcededYesTeam must average at most N goals conceded per match.
maxIymsSurpriseRateYesMax real-surprise (only 1/2 or 2/1) fraction. Use for 'IY/MS tutarlı' teams.
maxTotalGoalsScoredYesTeam must have scored at most N goals total in last inLast matches.
minAvgGoalsConcededYesTeam must average at least N goals conceded per match.
minIymsSurpriseRateYesFraction (0-1) of last N matches with a REAL IY/MS sürpriz: ONLY 1/2 or 2/1 (önde olan takım kaybeder). X/1, X/2, 1/X, 2/X, X/X are NOT surprises. E.g. 0.4 = at least 2 of last 5.
minTotalGoalsScoredYesTeam must have scored at least N goals TOTAL in last inLast matches. E.g. minTotalGoalsScored=6 for 'son 5 maçında toplam 6+ gol atan'.
maxFailedToScoreRateYesFraction (0-1) of matches where team failed to score.
maxTotalGoalsConcededYesTeam must have conceded at most N goals total in last inLast matches.
minMatchesScoredAboveYesTeam must have scored ≥ minGoalsPerMatch goals in at least N of the last inLast matches. E.g. minGoalsPerMatch=2, minMatchesScoredAbove=3 for 'son 5 maçının 3'ünde 2+ gol'.
minTotalGoalsConcededYesTeam must have conceded at least N goals total in last inLast matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 two genuinely useful behavioral facts: it scans only upcoming matches, and results do not carry enough to open a match directly — the agent must fetch matchKey from list_matches. It says nothing about the interaction of the 25 filters, result caps beyond the 'limit' default, or performance on broad date ranges.

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?

Two sentences, purpose front-loaded, then the chaining hint. No filler at all despite a 25-parameter surface, and the stat families are enumerated compactly rather than restated one by one.

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?

For a tool with 25 required-but-nullable parameters and no output schema, the description omits two things an agent needs: that conditions are AND-combined (narrow combinations can return nothing) and which trailing parameters can be left null in practice. The matchKey chaining note partially compensates, but the filtering semantics remain underspecified.

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%, so every one of the 25 parameters is already documented in the schema with examples and units. The description only groups them into families (averages, BTTS, clean sheet, İY/MS surprise), which adds orientation but no semantics beyond the schema; 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?

Opens with a specific verb+resource ('Yaklaşan maçları ... tarar') and enumerates the exact stat families used as filters (attığı/yediği ortalama gol, karşılıklı gol oranı, gol yemediği maç oranı, İY/MS sürprizi). It implicitly separates itself from goal-history/odds siblings by naming goal-form criteria, but never names an alternative tool, so differentiation is inferred rather than stated.

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 implied only: 'Yaklaşan maçları' establishes the upcoming-fixture scope, and the second sentence explains the downstream step (take matchKey from list_matches to open a result). There is no explicit when-to-use-this-vs-find_fixtures_by_form / _by_odds / _by_previous_scores guidance, which matters given five near-identical find_fixtures_* siblings.

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