Skip to main content
Glama

Oran Analiz Bot

find fixtures combined

find_fixtures_combined
Read-only

En güçlü tarama: form, gol istatistiği ve oran şartlarını tek taramada birleştirir (ör. son 3 maçı kazanmış ve 2,5 Üst oranı 1,70 altında). 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>",
      "formSide": "<formSide>",
      "formPattern": "<formPattern>",
      "minConsecutiveWins": "<minConsecutiveWins>",
      "minConsecutiveLosses": "<minConsecutiveLosses>",
      "minWins": "<minWins>",
      "inLastForm": "<inLastForm>",
      "inLastGoals": "<inLastGoals>",
      "minAvgGoalsScored": "<minAvgGoalsScored>",
      "maxAvgGoalsConceded": "<maxAvgGoalsConceded>",
      "minAvgTotalGoals": "<minAvgTotalGoals>",
      "minBttsRate": "<minBttsRate>",
      "oddsMarket": "<oddsMarket>",
      "oddsOutcome": "<oddsOutcome>",
      "oddsMinOdd": "<oddsMinOdd>",
      "oddsMaxOdd": "<oddsMaxOdd>",
      "league": "<league>",
      "limit": "<limit>"
    },
    "name": "find_fixtures_combined"
  }
}

Input Schema

NameRequiredDescriptionDefault
datesYesYYYY-MM-DD dates to scan.
limitYesMax results. Default 30.
leagueYesOptional league/country filter.
minWinsYesMin wins within inLastForm matches.
formSideYesWhich team's form to check. Null = either.
inLastFormYesWindow for minWins. Default 5.
oddsMarketYesMarket name to filter on, e.g. '2.5 Alt/Üst', 'Maç Sonucu', 'Karşılıklı Gol'.
oddsMaxOddYesMaximum odd value for that market/outcome.
oddsMinOddYesMinimum odd value for that market/outcome.
formPatternYesExact W/D/L pattern, newest-first. E.g. 'WWW'.
inLastGoalsYesRecent match window for goals stats. Default 5.
minBttsRateYesBTTS fraction (0-1) ≥ N.
oddsOutcomeYesOutcome within the market, e.g. 'Üst', '1', 'Var'. Null to match any outcome in the market.
minAvgTotalGoalsYesAvg total goals per match ≥ N.
minAvgGoalsScoredYesTeam avg goals scored ≥ N.
minConsecutiveWinsYesMin consecutive wins from most recent.
maxAvgGoalsConcededYesTeam avg goals conceded ≤ N.
minConsecutiveLossesYesMin consecutive losses.

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that conditions are combined in one pass and how to chain into other tools via matchKey, but says nothing about scan cost, how many dates are practical, or what the result set looks like.

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 tool's distinguishing capability, followed by the cross-reference tip. The example is compact and earns its place; 'En güçlü tarama' is slightly promotional but costs little.

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 an 18-parameter scan with no output schema, the description covers the core concept and the matchKey handoff but omits what a result contains and the fact that all 18 keys are required (many only nullable), which materially affects how the call must be constructed.

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 18 parameters is already documented inline. The description only contributes a single illustrative combination of parameters; it adds no semantics for the nullable-but-required quirk of passing nulls.

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?

States a concrete action and scope: it merges form, goal statistics and odds conditions into a single scan, with a worked example (won last 3 and 2.5 Üst odds under 1.70). That distinguishes it from the single-dimension siblings (find_fixtures_by_form, find_fixtures_by_goals_form, find_fixtures_by_odds) by implication, though it never explicitly names the superset relationship.

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?

The phrase 'en güçlü tarama' plus the conjunctive example implies it is the tool to pick when several criteria must hold at once, and it says to pull matchKey from list_matches to open a result elsewhere. There is no explicit when-not guidance or statement that the narrower siblings should be preferred for single-criterion scans.

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