Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_mma_card

Retrieve detailed bout information from an MMA fight card, including fighters, weight class, and results. Filter by main card, prelims, or early prelims.

Instructions

SofaScore MMA card. Returns the bouts of one MMA fight card, main event first, narrowed with part to all bouts, the maincard, the prelims or the earlyprelims. Each bout has the fighters (country, nickname, ranking where 0 is the champion, record), weight class, scheduled rounds, status, and for finished bouts the winner, win type, final round and fight time. Get org_id and card_id from sofascore-mma-schedule. Returns 404 when the card is unknown or has no bouts in that segment (for example a card without early prelims).

Input Schema

NameRequiredDescriptionDefault
partYesWhich segment of the card to return
org_idYesNumeric SofaScore MMA organisation id
card_idYesNumeric card id (card_id) from sofascore-mma-schedule

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.3/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 a solid job: it discloses ordering (main event first), the full shape of each bout (fighters with country/nickname/ranking/record, weight class, rounds, status, winner/win type/round/time), and the important 404 failure mode when a card is unknown or has no bouts in that segment. It omits auth and rate-limit context, so not 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?

Three sentences, front-loaded with the resource and return shape, then the segment parameter, then the error behavior. Dense but every sentence earns its place; no filler. Slightly heavy phrasing keeps it from a 5.

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, the description must describe returns, which it does thoroughly (per-bout fields plus segment behavior), and it covers the key 404 edge case. It would be complete with a note on whether results paginate or how fighters are identified, so a 4 is warranted.

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 baseline is 3; the description adds value by explaining what each `part` enum value means in terms of card segments and by clarifying the origin of org_id and card_id ('from sofascore-mma-schedule'). That is meaningfully more than the terse schema descriptions provide.

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+resource: returns the bouts of one MMA fight card, with main event first. It explicitly distinguishes itself from the sibling sofascore_mma_schedule by naming it as the source of org_id and card_id, so an agent can tell them apart without inspecting schemas.

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

Usage Guidelines4/5

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

Gives clear context: 'narrowed with `part` to all/maincard/prelims/earlyprelims' states how to select the desired segment, and it tells the agent where to obtain org_id and card_id (sofascore-mma-schedule). It lacks explicit when-not guidance or a named alternative for whole-event data, so it falls just short of a 5.

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