Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_mma_schedule

Find the main event of every MMA fight card on SofaScore for an organisation in a given month; returns card ID, fighters, weight class, rounds, status, and results.

Instructions

SofaScore MMA schedule. Returns the main event of every fight card an MMA organisation holds in one calendar month, with the card id and name, fighters (country, nickname, ranking where 0 is the champion, record), weight class, scheduled rounds, status, and for finished fights the winner, win type and final round. Find organisation ids (UFC 19906, PFL 19910, ONE 20269, Rizin 19905, Fight Nation Championship 20463, KSW 19946, OKTAGON 20258, Absolute Championship Akhmat 20254, Cage Warriors 19909, Dana White's Contender Series 20264, Brave CF 20267, Jungle Fight 20253) with sofascore-categories (sport mma) and sofascore-category-tournaments (category 1708). Use the card_id with sofascore-mma-card to read every bout. Returns 404 when the organisation has no card in that month or the id is not an MMA organisation.

Input Schema

NameRequiredDescriptionDefault
monthYesCalendar month as YYYY-MM
org_idYesNumeric SofaScore MMA organisation id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the returned field set (card id/name, fighter details, weight class, rounds, status, winner/win type/final round for finished fights) and the 404 error semantics. It omits auth requirements, rate limits, and pagination, which keeps it short of a 5.

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?

Front-loaded with the core behavior, then routing info, then error handling. The long parenthetical org-id list is dense but genuinely useful reference data; overall it is efficient though the run-on enumeration costs some readability.

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?

With no output schema and no annotations, the description must supply return and error semantics, and it does so thoroughly. The main residual gap is operational context such as rate limits or whether the month is interpreted in a specific timezone.

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 real value by supplying twelve concrete org_id example values (UFC 19906, PFL 19910, etc.) that the schema does not carry, plus the semantic note that ranking 0 means champion. It adds little about the `month` format beyond what the schema already states.

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?

States a specific verb and resource with precise scope: 'Returns the main event of every fight card an MMA organisation holds in one calendar month.' It enumerates the returned fields and distinguishes itself from the sibling sofascore_mma_card, which reads individual bouts.

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

Usage Guidelines5/5

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

Gives an explicit workflow: find org ids via sofascore-categories (sport `mma`) and sofascore-category-tournaments (category 1708), then pass `card_id` to sofascore-mma-card for every bout. It also names the exact failure condition (404 when no card that month or not an MMA org), so the agent knows when this tool does not apply.

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

Deploy Server

Other Tools