Skip to main content
Glama

betrend sports data

Live scores

live_scores
Read-onlyIdempotent

Matches being played right now on betrend, with the current score and minute or period. Optional filters: sport (e.g. football, cricket, basketball, ice-hockey, tennis, esports) and competition (betrend URL from search). Major competitions come first. Each match has its betrend.im page URL.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum matches to return, default 25.
sportNoSport code, e.g. football, cricket, basketball, ice-hockey, tennis, esports.
competitionNoCompetition URL from search, or its slug together with sport.

Output Schema

NameRequiredDescriptionDefault
as_ofYesWhen betrend produced this answer, UTC ISO 8601.
noticeNoHow to narrow the request when truncated.
matchesYes
has_moreNoPresent and true when more items exist than returned; narrow the filters.
truncatedNoPresent and true when the longest list was cut to keep the answer under 20000 bytes.
live_countYesAll live matches that fit the filters, before the limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / matches / items / properties / away / properties / url / description
      Previous value: -"betrend.im page of the team; cite it."New value: +"betrend.im page URL of the team."
    • changedOutput schema / properties / matches / items / properties / competition / properties / url / description
      Previous value: -"betrend.im page of the competition; cite it."New value: +"betrend.im page URL of the competition."
    • changedOutput schema / properties / matches / items / properties / home / properties / url / description
      Previous value: -"betrend.im page of the team; cite it."New value: +"betrend.im page URL of the team."
    • changedOutput schema / properties / matches / items / properties / url / description
      Previous value: -"betrend.im match page; cite it."New value: +"betrend.im match page URL."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavior: results are ordered with major competitions first and each match carries its betrend.im page URL — ordering is not something the annotations or typical schema express.

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?

Three short sentences, purpose front-loaded, filters second, ordering/detail third. No filler, though the closing sentence about page URLs is mild overlap with the output schema.

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 read-only, zero-required-parameter listing tool with a full schema and an output schema, the description covers scope, filters, ordering, and result contents. The only gap worth noting is no mention of default/paging behavior, which the schema handles via the limit default.

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 description coverage is 100%, so the schema already documents limit, sport, and competition, and the description's sport list and 'competition URL from search' phrasing largely restate it. The only marginal value is reinforcing that competition may be a URL obtained from the search tool, so baseline 3 applies.

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?

States a specific resource with scope: 'matches being played right now', plus what each result carries (score, minute/period, page URL). The 'right now' framing implicitly separates it from matches_by_date and match_details, though no sibling is named outright.

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?

It labels sport and competition as 'optional filters' and points to search as the source of a competition URL, which gives an implied retrieval flow. There is no explicit when-to-use-this vs. matches_by_date/match_details guidance or statement of exclusions.

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