Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora.mcp
OverviewDiscussionsAdmin

lolesports_schedule

Read-only

Returns League of Legends esports matches around today: start time, state (unstarted, inProgress, completed), block name, league, teams with game wins and best-of format. Optionally filter by league_id from lolesports_leagues (one id, or up to 10 comma-separated ids to combine leagues). Follow older_page_token or newer_page_token from the response to page backward or forward; a missing token means that direction is exhausted. Use lolesports_live for only in-progress games.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lolesports_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
hlNoOptional language code; defaults to en-US.
league_idNoOptional league id from lolesports_leagues, or up to 10 comma-separated ids to combine leagues (for example LEC and LCK); omit for all leagues.
page_tokenNoOptional older or newer cursor copied from the previous schedule response.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / league_id / description
      Previous value: -"Optional league id from lolesports_leagues; omit for all leagues."New value: +"Optional league id from lolesports_leagues, or up to 10 comma-separated ids to combine leagues (for example LEC and LCK); omit for all leagues."
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's extra value is what it discloses about results and paging: the enumerable match states and the rule that a missing older/newer token means that direction is exhausted. That paging semantic is genuinely behavioral and not derivable from annotations. It stops short of noting auth, rate limits, or how far 'around today' extends.

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?

Four sentences, each carrying distinct information: payload, filtering, pagination, and the alternative tool. The primary use case and result contents are front-loaded with 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 and all three parameters optional, the description covers what an agent needs to call it correctly: filter source, paging mechanics, and the sibling alternative. The only gaps are the unmentioned hl parameter and how precisely the 'around today' time window is bounded.

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; the description earns above that by explaining that the two cursor tokens move in opposite directions and that an absent token terminates paging, which the schema only gestures at. It also restates the league_id multi-id combining rule, though it never mentions the hl language parameter.

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 ('Returns League of Legends esports matches around today') plus the concrete payload fields (start time, state, block, league, teams, best-of). It explicitly names the sibling it is not ('Use lolesports_live for only in-progress games'), so the agent can route between the two without opening a schema.

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 clear when-to-use and when-not-to-use guidance: this tool for the day's schedule, lolesports_live for in-progress only, and league_id values sourced from lolesports_leagues. It also states the default behavior when no filter is supplied ('omit for all leagues').

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

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