Crawlora MCP

sofascore_mma_card

Read-only

Returns the bouts of one MMA fight card, main event first, narrowed with part to all, maincard, prelims or earlyprelims: fighters with ranking and record, weight class, scheduled rounds and the result of finished bouts. Requires org_id and a card_id from sofascore_mma_schedule; a not-found error means an unknown card or one without that segment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "org_id": "<org_id>",
      "card_id": "<card_id>",
      "part": "<part>"
    },
    "name": "sofascore_mma_card"
  }
}

Input Schema

Name	Required	Description
`part`	Yes	Required. Card segment. One of all, maincard, prelims, earlyprelims.
`org_id`	Yes	Required. Numeric SofaScore MMA organisation id, e.g. 19906 for UFC.
`card_id`	Yes	Required. Numeric card id (card_id) from sofascore_mma_schedule, e.g. 197311.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, openWorldHint), yet the description adds genuine behavioral context: results are ordered main event first, and a not-found error implies either an unknown card or a missing segment. These are non-obvious traits an agent could not get from annotations alone.

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?

Two dense sentences, purpose front-loaded, followed by prerequisites and error semantics. Every clause carries information; slightly packed but no filler.

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 an output schema present, return-field details are largely redundant, yet ordering, prerequisite, and error interpretation are all covered. Complete enough to invoke correctly; only explicit alternative guidance 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 coverage is 100%, so all three required params are already documented, including the part values. The description mirrors these (all/maincard/prelims/earlyprelims) and adds the provenance of card_id, but adds little parameter meaning beyond the schema.

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?

Specific verb+resource ('Returns the bouts of one MMA fight card') with an explicit scope qualifier (main event first) and a named prerequisite sibling (sofascore_mma_schedule). An agent can distinguish this from sofascore_mma_schedule without opening either schema.

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?

Clearly states the prerequisite chain: org_id plus a card_id sourced from sofascore_mma_schedule, and explains that a not-found error means an unknown card or a card lacking that segment. It stops short of explicitly naming when-not-to-use or contrasting alternatives beyond the ID source.

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

All Crawlora MCP 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?