Skip to main content
Glama

The AI's graded track record

get_ai_track_record
Read-onlyIdempotent

How often the Kickwise AI's picks made before kickoff were right: the high confidence record (picks of 65% or more), every call over the last 30 days and all time, a comparison with always picking the home team, the leagues with most calls, and the latest graded calls.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for card labels, team names, AI summaries and linked kickwise.ai pages. Pass the user's requested language when it is en, es, fr, ar or pt; for any other language pass en and translate the relevant text in your answer. An explicit lang overrides the client locale. When omitted, a supported client locale is used, else en.

Output Schema

NameRequiredDescriptionDefault
noteYes
sinceYes
recentYes
csv_urlYes
leaguesYes
all_timeYes
record_urlYes
updated_atYes
last_30_daysYes
high_confidenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: which statistical cuts are aggregated (confidence threshold, 30-day vs all-time windows, home-team baseline, league breakdown, latest graded calls). It stops short of describing freshness/lag for 'latest' or any pagination, which is the only remaining gap.

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?

It is a single dense sentence that front-loads the core question ('how often the picks were right') before listing the breakdowns. No filler or repetition. The colon-and-list construction is slightly hard to scan, but every clause names a distinct content category that the agent can use.

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?

An output schema exists, so return shape and field meanings need not be explained, and the description instead spends its budget on what categories of record are included — the right choice for an aggregate-stats tool. Combined with annotation coverage of the safety profile, an agent can call this correctly. Only the missing alternative-tool routing keeps it from a 5.

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?

There is only one parameter and schema coverage is 100%, with the schema itself spelling out the enum, override behavior, and the 'pass en and translate' fallback. The description says nothing about language handling, so it adds no meaning beyond the schema. Baseline 3 applies when the schema carries the whole burden.

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 resource — the Kickwise AI's graded pick record — and enumerates its contents: high-confidence record (65%+), last-30-days and all-time calls, a home-team baseline comparison, per-league counts, and latest graded calls. That is far more specific than a tautology. It does not, however, distinguish itself from siblings like get_predictions or get_match_prediction, so an agent must infer the split from names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: an agent can deduce this is the tool for 'how accurate is the AI?' questions rather than for a single match forecast. There is no explicit when-to-use statement, no exclusion such as 'for a single fixture use get_match_prediction', and no note on prerequisites or cost. Adequate but leaves routing to inference.

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