Skip to main content
Glama

Oran Analiz Bot

Ortak Rakipler

common_opponents
Read-only

Uygulamadaki 'Ortak Rakipler': iki takımın aynı rakiplere karşı sonuçları (iç saha/deplasman, skorlar, gol farkı), aynı kupon sonucunu yapan (hibrit) eşleşmeler ve ev takımı lehine ortalama gol farkı üstünlüğü. Varsayılan maçın sezonu; başka sezonlar yanıttaki availableSeasons'tan adıyla eklenir.

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

Input Schema

NameRequiredDescriptionDefault
seasonsNoSezon adları (yanıttaki availableSeasons'tan).
matchKeyYeslist_matches'ten alınan matchKey.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 useful behavior beyond that: the default scope is the match's own season and alternate seasons must be named from the availableSeasons field in the response. It says nothing about failure modes for an invalid or unknown matchKey.

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?

Two sentences, with the analytical scope front-loaded and the season-default rule placed last where it belongs. The first sentence is dense with parenthetical enumerations but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, no-output-schema tool the description does outline what comes back (per-opponent results, hybrid pairings, average goal-difference edge) and explains season selection. It omits how the two teams are determined from matchKey and what happens on an invalid key, which leaves real gaps for an agent calling it blind.

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 is 3, but the description adds a genuinely new fact not in the schema: seasons default to the match's season rather than requiring explicit input. The matchKey semantics are left entirely to the schema, so it is not quite a 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 concrete analysis resource and enumerates its dimensions (results vs shared opponents with home/away split, scores, goal difference, hybrid same-coupon pairings, and the home team's average goal-difference edge), so an agent knows what it produces. It never states that the two teams are derived from the supplied matchKey, and it does not name any sibling it should be preferred over, which keeps it below 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named even though siblings such as similar_matches or find_fixtures_by_previous_scores occupy adjacent ground. Usage is only implied by the noun description of the analysis type.

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