Skip to main content
Glama

Oran Analiz Bot

Oran kalibrasyonu

odds_calibration
Read-only

Uygulamadaki oran kalibrasyonu: bir market sonucu için oran belirli aralıktayken geçmişte kaç maçta tuttuğu (isabet yüzdesi, maç sayısı, ortalama oran). Ör. 'MS 1 oranı 1,50–1,60 iken ev sahibi ne sıklıkla kazandı'. Market verilmezse o büro/aşamanın kalibrasyon marketleri (anahtar + etiket) listelenir. provider/stage ile istenen büronun oranlarıyla hesaplanır (varsayılan nesine kapanış).

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_calibration"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageNoVarsayılan closing.
marketNoMarket anahtarı ya da etiketi (ör. ms_1 ya da 'Maç Sonucu: 1 (Ev)').
maxOddNo
minOddNo
providerNoBüro providerKey (ör. nesine, pinnacle, bet365). Varsayılan: nesine.
minMatchesNoSonucun anlamlı sayılması için en az maç.

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 the safety profile is covered. The description adds genuinely useful behavior: the default provider (nesine) and stage (closing), and the fallback listing behavior when `market` is absent. It does not discuss result volume, pagination, or what happens when too few matches exist beyond the schema's minMatches note.

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 definition is front-loaded with the core operation, then the example, then the fallback and defaults. Every sentence carries information, though the single long opening sentence packs several ideas together and could be split for faster scanning.

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 no output schema, the description usefully enumerates the returned metrics (hit percentage, match count, average odds) and explains both operating modes. For a 6-parameter, zero-required analytical tool this is close to complete; only edge-case behavior (insufficient sample, empty results) is left unstated.

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 67%, and the description compensates by explaining the market key/label format ('ms_1 ya da Maç Sonucu: 1 (Ev)'), the provider default, and the stage default. The minOdd/maxOdd range semantics are implied by the odds-range framing. minMatches is only explained in the schema, not the description, so it is not a full 5.

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 names a specific operation: computing historical hit rate (isabet yüzdesi, maç sayısı, ortalama oran) for a market outcome when the odds fell in a given range, and it also discloses a second mode (listing calibration markets when no market is supplied). That is a concrete verb+resource, well beyond restating the title. It does not explicitly contrast itself with siblings such as analyze_odds or realized_stats, which keeps it from 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?

Usage is made concrete with a worked example ('MS 1 oranı 1,50–1,60 iken ev sahibi ne sıklıkla kazandı') and with the rule that omitting `market` switches the tool into a market-listing mode. Defaults for provider and stage are stated. There is no explicit when-not-to-use guidance or named alternative, so it stops 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