Crawlora MCP

sofascore_mma_schedule

Read-only

Returns the main event of every fight card an MMA organisation holds in one month (month as YYYY-MM): card id and name, fighters with ranking and record, weight class, status and the result of finished fights. Requires an org_id such as 19906 for UFC, found with sofascore_category_tournaments for category 1708; use the card_id with sofascore_mma_card. A not-found error means no card that month or a non-MMA id.

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>",
      "month": "<month>"
    },
    "name": "sofascore_mma_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`month`	Yes	Required. Calendar month as YYYY-MM, e.g. 2026-10.
`org_id`	Yes	Required. Numeric SofaScore MMA organisation id, e.g. 19906 for UFC. Find ids with sofascore_category_tournaments for category 1708 (the MMA World category).

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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by disclosing the error semantics ('a not-found error means no card that month or a non-MMA id') and enumerating the returned fields, but omits any pagination or coverage caveats.

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 purpose, then params, then error handling. It is dense and packed into one long sentence with a colon list, but essentially every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-param read tool with a full schema and an output schema, the description covers purpose, id sourcing, downstream card_id use, and error meaning. Nothing an agent needs to call it correctly is missing.

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% and both params are documented there with the same UFC example (19906) and the category 1708 pointer. The description largely restates the schema, so it adds only the workflow linkage (card_id usage) rather than new parameter semantics.

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 (returns) and resource (the main event of every fight card an MMA organisation holds in a given month), including scope by org and month. It clearly distinguishes itself from sofascore_mma_card (per-card detail) and sofascore_category_tournaments (id discovery).

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?

Explicitly routes the agent: get org_id via sofascore_category_tournaments for category 1708, then feed the returned card_id to sofascore_mma_card. It also explains the not-found error condition, giving both when-to-use and failure interpretation.

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?