Skip to main content
Glama

Oran Analiz Bot

Maç oranları

match_odds
Read-only

Maçın oranları. provider olmadan: iddaa/nesine tablosu (her sonuç için güncel odd ve açılış openingOdd) ve bu maçta oranı olan TÜM büroların listesi (bureaus: providerKey + ad). provider ile (ör. pinnacle, bet365): o büronun açılış ve kapanış oranları (yalnız oynanmamış maçta; bitmiş maçta büro oranı verilmez). Büroları karşılaştırmak, açılış→kapanış hareketine bakmak ya da analiz için market/sonuç adını öğrenmek için kullan. Büro: oranlar tek bir büroya bağlı değildir; iddaa (açılış), nesine (kapanış, varsayılan) ve 40'a yakın uluslararası büro (pinnacle, bet365, 1xbet, betfair ...) vardır. Maçta hangi büroların oranı olduğu match_odds çıktısındaki bureaus listesindedir.

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": {
      "matchKey": "<matchKey>"
    },
    "name": "match_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
matchKeyYeslist_matches'ten alınan matchKey.
providerNoİsteğe bağlı büro: `bureaus` listesindeki providerKey ya da ad (ör. pinnacle, bet365).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 real behavioral value beyond that by disclosing a conditional rule: bureau odds are only returned for unplayed matches, and finished matches yield no bureau odds. That is useful, but it does not cover other traits such as what the default bureau (nesine) means for the returned table or any partial-availability caveats.

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 two-mode structure is front-loaded and dense with payoff, and each sentence carries operational information. It is long-ish and the sentence explaining that odds are not tied to a single bureau is slightly convoluted, but nothing is 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?

For a two-parameter read tool with no output schema, the description covers mode behavior, returned field names, availability constraints, and the default bureau convention. An agent could call this correctly and interpret the result without further documentation.

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, but the description earns an extra point by explaining the semantic effect of `provider`: omitted means the aggregated table plus bureau list, supplied means single-bureau opening/closing odds, with concrete example values (pinnacle, bet365) and the pointer that valid keys come from the `bureaus` output list.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a concrete verb+resource and immediately splits the tool into two distinct modes: no `provider` returns the iddaa/nesine table plus a `bureaus` list, while `provider` returns that single bureau's opening and closing odds. The specific field names (`odd`, `openingOdd`, `bureaus`, `providerKey`) make it unmistakable versus siblings like match_detail.

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?

Explicitly states when to use it: comparing bureaus, inspecting opening-to-closing movement, or learning market/result names for analysis. It gives clear contexts but stops short of naming any sibling alternative or exclusion (e.g., when another odds tool is preferable), leaving the routing to the reader.

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