Skip to main content
Glama

Oran Analiz Bot

find fixtures by odds

find_fixtures_by_odds
Read-only

Bir marketteki sonucun oranı belirli aralıkta olan yaklaşan maçları bulur (ör. MS 1 oranı 1,50–1,80). Market ve sonuç adlarını match_odds ya da filter_markets'teki gibi birebir kullan. 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": {
      "date": "<date>",
      "marketName": "<marketName>",
      "outcome": "<outcome>",
      "minOdd": "<minOdd>",
      "maxOdd": "<maxOdd>",
      "limit": "<limit>"
    },
    "name": "find_fixtures_by_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesYYYY-MM-DD. Null for today.
limitYesMax results to return.
maxOddYesMaximum odd value (inclusive).
minOddYesMinimum odd value (inclusive).
outcomeYesOutcome/selection, e.g. 'Üst', 'Alt', '1', 'X', '2', 'Var', 'Yok', '1/1', 'X/2'.
marketNameYesExact market name, e.g. '2.5 Alt/Üst', 'Maç Sonucu', 'Karşılıklı Gol'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 a real behavioral constraint — market/outcome strings must match existing tool vocabulary exactly, so inexact names presumably yield nothing — but says nothing about result ordering, empty-result handling, or truncation beyond the limit parameter.

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?

Three tight sentences: purpose with example first, naming convention second, follow-up path third. No filler and nothing repeated from the schema.

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?

For a six-required-parameter read-only search tool with a fully documented schema and no output schema, the description covers what it returns (upcoming matches), naming prerequisites, and how to chain to matchKey lookups. Only return-shape and result-ordering details are absent, which is acceptable given schema coverage.

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 coverage is 100% and every parameter has its own description, so the baseline is 3. The description only reinforces the 'exact name' requirement for marketName/outcome and illustrates the numeric range, which is marginally more than the schema already conveys.

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 specific verb+resource+filter: finds upcoming matches whose outcome odds in a given market fall inside a numeric range, with a concrete example ('MS 1 oranı 1,50–1,80'). That clearly separates it from the form/goals/scores fixture finders, though it does not explicitly name those alternatives.

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 actionable pre-call guidance: use market and outcome names exactly as they appear in match_odds or filter_markets, and fetch matchKey from list_matches (date + team name) to open a given outcome elsewhere. It stops short of stating when to prefer this tool over find_fixtures_combined or the other find_fixtures_* variants.

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