Skip to main content
Glama

Oran Analiz Bot

Oran Ara

odds_search
Read-only

Uygulamadaki 'Oran Ara': belirli bir maç olmadan oran şartlarıyla arama (her şart market + sonuç + oran aralığı; hepsi birlikte sağlanmalı). mode=current: verilen günün maçlarında şartlara uyanlar (ülke/lig/durum süzgeci). mode=historical: geçmişte bu oranlarla oynanmış maçlar ve nasıl bittikleri (genel istatistikler dahil); kapsam ülke, lig, takım, H2H ile verilir, lig ve takım ADLA yazılır (hangi kaydın kullanıldığı resolved'da); geçmiş aramada satırlar maç, tarih ve skor taşır, oran değeri taşımaz. provider/stage ile istenen büronun oranlarında aranır (varsayılan kapanışta nesine, açılışta iddaa). Bazı aramalar arka planda taranır: bitmezse jobId döner, aynı aracı yalnız jobId ile tekrar çağır.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "odds_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNocurrent için gün (varsayılan bugün).
modeNoVarsayılan current.
pageNohistorical: sayfa (30'luk). İstatistikler ilk sayfada tüm eşleşmeler üzerindendir.
jobIdNoBitmemiş taramanın numarası; verilirse yalnız onun durumu/sonuçları döner.
stageNoVarsayılan closing.
leagueNocurrent: yalnız bu ligin maçları.
countryNocurrent: yalnız bu ülkenin maçları.
filtersNoOran şartları; hepsi birlikte sağlanmalı. Market/sonuç adları filter_markets'teki gibi.
providerNoBüro providerKey (ör. nesine, iddaa, pinnacle, bet365, 1xbet). Varsayılan: güncelde kapanışta nesine, geçmişte bet365; açılışta iddaa.
matchStatusNocurrent: maç durumu süzgeci.
historicalScopeNohistorical: kapsam. Lig ve takımı adıyla ver.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial context beyond that: long searches are scanned in the background and return a jobId, historical rows carry match/date/score but deliberately omit the odds value, and league/team must be supplied by name with the resolved record surfaced in `resolved`. It also discloses mode-stage-dependent provider defaults. Nothing contradicts the read-only annotation.

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 description is front-loaded with the core definition, then mode behavior, then provider defaults and the background-job caveat in priority order. Sentences are long and parenthetical-heavy, but each carries operational information rather than filler.

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

Completeness5/5

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

With 11 parameters, nested objects, and no output schema, the description still tells the agent what a result row contains, where statistics come from, what `resolved` is for, and how to resume an unfinished scan. That is sufficient to invoke the tool correctly in either mode.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds cross-parameter meaning by tying provider/stage defaults together (closing→nesine, opening→iddaa) and by explaining that historical scope takes names rather than IDs, with resolution reported back. It does not mention the historical default provider (bet365) or the page cap, so the added value is real but partial.

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 states a specific operation: searching by odds conditions (market + outcome + odds range, all conjunctive) without a fixed match, and splits it into current vs historical modes. An agent can tell what the tool returns in each mode. It does not differentiate itself from sibling tools such as find_fixtures_by_odds, so it stops short of a 5.

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?

Mode selection is explained concretely: mode=current for a given day's fixtures with country/league/status filters, mode=historical for matches previously played at these odds plus how they ended. It also states the recovery path for long scans (re-call with only jobId). It gives no explicit exclusion against sibling tools, which keeps it below 5.

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