betrend sports data

Fixtures and results by date

matches_by_date

Read-onlyIdempotent

Fixtures and results on betrend for one UTC calendar day (Y-m-d), from 3 years ago to 14 days ahead. Optional filters: sport, competition and team (betrend URLs from search). Major competitions come first. Each match has its betrend.im page URL.

Input Schema

Name	Required	Description
`date`	Yes	UTC day, Y-m-d, e.g. 2026-10-11.
`team`	No	Team URL from search, or its slug together with sport.
`limit`	No	Maximum matches to return, default 50.
`sport`	No	Sport code, e.g. football, cricket, basketball, ice-hockey, tennis, esports.
`competition`	No	Competition URL from search, or its slug together with sport.

Output Schema

Name	Required	Description
`date`	Yes
`as_of`	Yes	When betrend produced this answer, UTC ISO 8601.
`notice`	No	How to narrow the request when truncated.
`matches`	Yes
`has_more`	No	Present and true when more items exist than returned; narrow the filters.
`truncated`	No	Present and true when the longest list was cut to keep the answer under 20000 bytes.
`match_count`	Yes	All matches that fit the filters on this day, before the limit.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 18, 2026
- 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."
```
First observedOct 12, 2026

TDQS

A3.8/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 description's job is to add context. It does: the queryable date range, the ordering rule (major competitions first), and the per-match URL give behavior the annotations cannot express.

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 dense sentences, front-loaded with the core resource and time scope, then filters, then ordering and output detail. No filler sentences.

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-value detail is not needed; the description still notes the per-match URL and ordering, which is a bonus. The only gap is routing guidance against siblings, which is absent.

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 all five parameters including date format, limit bounds, and filter inputs are already documented. The description largely restates sport/competition/team without adding syntax or selection nuance beyond what the schema provides.

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 verb+resource with explicit scope: fixtures and results for one UTC calendar day on betrend. The date-bounded listing is clearly distinct in spirit from live_scores and match_details, but no sibling is named to make the distinction unambiguous.

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?

The description implies usage by stating the date window (3 years back to 14 days ahead) and listing optional filters, but never says when to prefer this over live_scores or team/competition-scoped siblings. Usage is inferable, not prescribed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All betrend sports data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?