Skip to main content
Glama

Oran Analiz Bot

Benzer maçlar

similar_matches
Read-only

Uygulamadaki 'Benzer Maçlar': oran profili (birçok marketin oranları birlikte) bu maça en çok benzeyen geçmiş maçlar, sonuçları ve genel istatistikleri. analyze_odds birkaç seçili orana bakar, bu araç maçın bütün oran profiline bakar. Büro seçimi uygulamadaki gibi: provider tek büro (varsayılan kapanışta nesine); providers birden çok büro = yalnız bu bürolarin HEPSİNDE benzer olan ortak maçlar; allProviders = 'Tüm Bürolar (Ortak)', maçta oranı olan tüm bürolarda ortak; compare = 'Büro Karşılaştır', her büronun sonucu ayrı (byProvider). Kapsam (aynı hakem, lig, takımlar ...) ve zaman aralığı verilebilir; k en fazla 15.

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": "similar_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNoBenzer maç sayısı (varsayılan 15).
modeNoAçılış ya da kapanış oranı profili.
filterNoGeçmiş maçların kapsamı (uygulamadaki gibi). Verilmezse tüm maçlar.
compareNoBüro Karşılaştır: ortak küme yerine her büronun benzer maçları ayrı döner (`byProvider`). providers ya da allProviders ile kullanılır.
matchKeyYeslist_matches'ten alınan matchKey.
providerNoİsteğe bağlı tek büro providerKey (match_odds `bureaus`, ör. pinnacle). Varsayılan: kapanışta nesine.
providersNoBirden çok büro providerKey, ör. ["nesine", "pinnacle", "bet365"]: bu bürolarin hepsinde ortak benzer maçlar (compare ile: ayrı ayrı).
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.
allProvidersNoTüm Bürolar (Ortak): maçta bu aşamada oranı olan bütün bürolar (compare ile: hepsi ayrı ayrı).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare this a read-only, non-open-world operation; the description adds useful behavior beyond that: it compares the whole odds profile, returns historical results and aggregate stats, defaults to nesine at closing, caps k at 15, and returns per-provider results under compare. It does not describe result ordering, failure cases, or provider-availability behavior.

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 tool's purpose and its contrast to analyze_odds, and every subsequent sentence carries useful bureau or scope information. It is a dense paragraph with semicolon-separated clauses rather than clearly structured sections, which slightly reduces scanability.

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 9-parameter tool with a nested filter object and no output schema, the description covers the comparison basis, bureau modes, scope options, time range, and result cap. It is complete enough to call correctly, but the exact shape of the returned statistics and per-provider output could be clearer.

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 would be 3, but the description adds real meaning by explaining how provider, providers, allProviders, and compare interact, including the default provider and the shared-vs-separate result behavior. It also clarifies that scope filters and timeRange can be supplied, though it does not add semantics for every individual filter field.

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 states a specific action: finding historical matches whose full odds profile most closely resembles the given match, including results and general statistics. It explicitly distinguishes this from analyze_odds by contrasting a few selected odds with the entire odds profile, so an agent can tell the tools apart without opening either schema.

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 gives a clear when-to-use signal against analyze_odds and explains the bureau-selection modes (provider, providers, allProviders, compare) in enough detail to choose among them. It does not cover when to prefer other fixture-search or odds-search siblings, nor does it state exclusions, so it stops short of the top score.

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