Skip to main content
Glama

Oran Analiz Bot

Büro karşılaştırma

compare_bureaus
Read-only

Aynı seçimlerle oran analizini birden çok büroda ayrı ayrı çalıştırır ve sonuçları yan yana verir; her büro kendi oranı ve kendi oran geçmişiyle analiz edilir. Bir oranın büroya göre farklı sonuç verip vermediğini görmek için kullan. Büroları match_odds bureaus listesinden seç. Büro marketi vermiyorsa o büro için hasOdds:false ve eksik seçimler döner. Kapsam, zaman aralığı ve tolerans analyze_odds'taki gibidir.

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>",
      "selections": "<selections>",
      "providers": "<providers>"
    },
    "name": "compare_bureaus"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
filterNoGeçmiş maçların kapsamı (uygulamadaki gibi). Verilmezse tüm maçlar.
matchKeyYeslist_matches'ten alınan matchKey.
providersYesBüro providerKey listesi, ör. ["nesine", "pinnacle", "bet365"] (match_odds `bureaus`).
timeRangeNoZaman aralığı: last_1_week | last_2_weeks | last_1_month | last_3_months | all_time (varsayılan) | last_N_days (ör. last_400_days) | between_YYYY-MM-DD_YYYY-MM-DD.
toleranceNoOran toleransı (oranın ± etrafı, ör. 0.05). Varsayılan: kullanıcının uygulamadaki ayarı.
selectionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/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. Beyond that, the description discloses meaningful result behavior: each bookmaker is analyzed against its own odds and odds history, and when a bookmaker does not offer the market, hasOdds:false plus missing selections are returned. For a tool with no output schema this return-shape disclosure is genuinely useful; only rate limits/pagination-like details are absent.

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?

Four sentences, front-loaded with the core behavior, then the use case, then the data source, then the edge case. Nothing is repeated from the name or schema and every sentence carries information an agent needs.

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?

With 7 parameters, a nested filter object and no output schema, the description does the important work: it explains the per-bookmaker result shape, the hasOdds:false fallback, and points to a sibling for the shared filter semantics. A little more on the shape of the side-by-side comparison would make it fully self-sufficient.

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 71%, so the schema carries most parameter meaning. The description adds the provenance of `providers` (the match_odds `bureaus` list) and delegates filter/timeRange/tolerance semantics to analyze_odds, which tells the agent those parameters behave identically rather than needing separate interpretation. This is a real addition beyond the schema, though indirect.

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?

The description names a specific operation — running the odds analysis on the same selections across multiple bookmakers and returning results side by side — and immediately scopes it ('her büro kendi oranı ve kendi oran geçmişiyle analiz edilir'). This distinguishes it clearly from its closest sibling analyze_odds, whose semantics it explicitly inherits only for scope, time range and tolerance.

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?

It states the selecting scenario plainly: use it to see whether an outcome's odds differ by bookmaker. It also tells the agent where to obtain the providers list (match_odds `bureaus`) and that scope/time-range/tolerance behave as in analyze_odds. No explicit when-not guidance (e.g. use analyze_odds for a single bookmaker), which keeps it short of a 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