Skip to main content
Glama

Oran Analiz Bot

Oran değişimleri

odds_changes
Read-only

Uygulamadaki 'Oran Takip': maçlardaki son iddaa oran değişimleri (maç, market, sonuç, eski ve yeni oran). Belirli bir maçın açılış→güncel farkı için match_odds daha uygundur.

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

Input Schema

NameRequiredDescriptionDefault
searchNoİsteğe bağlı takım, lig ya da market adı süzgeci (büyük/küçük harf duyarsız, kısmi). Belirli bir maç aranıyorsa kullan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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; the description adds genuine value by disclosing the returned fields (match, market, outcome, old and new odds). It stops short of stating how far back 'son' reaches or how many changes come back.

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?

Two sentences, front-loaded with the resource and its payload, followed immediately by the sibling disambiguation. Nothing is redundant.

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 one-parameter, read-only listing tool with no output schema, the description supplies both scope and return shape. The only remaining gap is the recency window and result volume, which an agent would want before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single search parameter is fully documented in the schema, so the schema does the heavy lifting. The description adds only a light usage cue ('Belirli bir maç aranıyorsa kullan') rather than new semantics, which is the baseline case.

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 resource ('son iddaa oran değişimleri') and enumerates exactly what each record carries (maç, market, sonuç, eski ve yeni oran). It also explicitly separates this tool from match_odds, so an agent can distinguish the two 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 an explicit redirect: for a single match's opening→current delta, use match_odds instead. That is clear conditional guidance, but it only covers one alternative case and leaves the boundary with the other odds-related siblings unstated.

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