Skip to main content
Glama

Oran Analiz Bot

Bülten Analizi

bulletin_scan
Read-only

Uygulamadaki 'Bülten Analizi': bir kayıtlı filtreyi adıyla (list_saved_filters) günün bültenindeki tüm maçlara (ya da matchKeys ile seçilenlere) uygular, maçları eşleşme sayısına göre sıralar. Kapsam/zaman/tolerans bu tarama için değiştirilebilir; compareProviders ile filtre birden çok büroda ayrı ayrı çalışır; analysisType=similar ile filtre yerine benzer maç taraması yapılır (similar.providers birden çok büro = ortak; similar.allProviders = Tüm Bürolar (Ortak); similar.compare = Büro Karşılaştır). Arka planda taranır: 90 saniyede bitmezse jobId döner, aynı aracı yalnız jobId ile çağırarak devam et. Yalnız premium üyelere açık.

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

Input Schema

NameRequiredDescriptionDefault
dateNoBülten günü (varsayılan bugün).
modeNoVarsayılan closing.
jobIdNoBitmemiş taramanın numarası; verilirse yalnız onun durumu/sonuçları döner.
filterNoFiltrenin kapsamını (favori taraf şartı dahil) bu taramada geçersiz kılar.
similarNoanalysisType=similar için.
matchKeysNoYalnız bu maçlar (list_matches'ten).
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ı.
partialOddsNoMaçta filtrenin bazı oranları yoksa kalanlarla analiz et.
savedFilterNoUygulanacak kayıtlı filtrenin adı (list_saved_filters; analysisType=filter için).
analysisTypeNoVarsayılan filter.
compareProvidersNoFiltreyi bu bürolarda ayrı ayrı çalıştır, ör. ["nesine", "pinnacle"] (kayıtlı filtre şart).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare only readOnlyHint=true and openWorldHint=false. The description adds substantial behavior that goes beyond them: the scan runs in the background, returns a jobId if it does not finish within 90 seconds, is resumable only via that jobId, results are sorted by match count, and the tool is restricted to premium members. This is exactly the operational context an agent needs before committing to a slow call.

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 dense but front-loaded: core behavior first, then mode variants, then background job behavior, then the premium restriction. Some long run-on parenthetical enumerations of the similar sub-modes cost readability, but almost every clause carries information an agent would otherwise have to infer.

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 12-parameter tool with nested objects and no output schema, the description covers the hard parts: mode selection, parameter overrides, multi-bureau behavior, async job resumption, and access gating. What is left implicit is the shape of the ranked results (for example, what fields come back per match) and whether large result sets are truncated.

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 description coverage is 100%, so the baseline is 3. The description still adds cross-parameter meaning that the schema does not supply: the filter object overrides the saved filter's scope, time, and tolerance for this scan only, compareProviders requires a saved filter, and the similar.providers, allProviders, and compare combinations map to distinct bureau semantics.

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 verb and resource: it applies a named saved filter to all matches in the day's bulletin (or to those selected via matchKeys) and ranks them by match count. It distinguishes the tool from siblings by naming list_saved_filters and list_matches as the sources and by explaining the internal analysisType=similar path, so an agent knows exactly what this tool produces.

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 clear conditions for use: a saved filter name is required for analysisType=filter, matchKeys narrows the scope, and compareProviders runs the filter separately per bureau. It also explains the resume path: call the tool again with only jobId if the job does not finish in 90 seconds. However, it never explicitly routes the agent to similar_matches or compare_bureaus when a single-match or bureau-only analysis is wanted.

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