Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

lolesports_news

Read-only

Returns the League of Legends Esports news page: up to the newest 100 articles with title, summary, link, publication time, banner image, authors and whether the item links out to another site (a video or a store page). Optionally set hl to a site language such as ja-JP and limit to keep only the newest items. The page has no category or tag filter. Use it for announcements and editorial news; use lolesports_schedule and lolesports_completed_events for matches.

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_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
hlNoOptional site language; one of cs-CZ, de-DE, el-GR, en-AU, en-GB, en-PH, en-SG, en-US (default), es-ES, es-MX, fr-FR, hu-HU, id-ID, it-IT, ja-JP, ko-KR, pl-PL, pt-BR, ro-RO, ru-RU, th-TH, tr-TR, vi-VN, zh-TW.
limitNoOptional number of newest articles to return, 1 to 100; defaults to all the page lists.

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. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real context beyond them: the 100-item cap, newest-first ordering, the absence of category/tag filtering, and the fact that some items link out to video or store pages. It stops short of disclosing rate limits or pagination/auth behavior, which keeps it at a 4 rather than 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with what is returned and what it cannot do, then the routing guidance. Every sentence carries information an agent would otherwise have to infer; nothing is padded.

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?

An output schema exists, so return-value documentation is not required, yet the description still summarizes the payload shape. With 0 required params, 2 optional params at full coverage, and annotations covering the safety profile, there is no gap an agent would hit when calling this tool.

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% and the schema already lists the full language enum and the 1-100 range for limit. The description only restates these ('hl to a site language such as ja-JP', 'limit to keep only the newest items'), adding minor clarity about truncation order but no syntax or default behavior 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?

States a specific verb and resource ('Returns the League of Legends Esports news page') and enumerates the returned fields (title, summary, link, publication time, banner image, authors, external-link flag). It also names the sibling tools it is not (lolesports_schedule, lolesports_completed_events), so an agent can distinguish it without opening any 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?

Explicitly routes the agent: 'Use it for announcements and editorial news; use lolesports_schedule and lolesports_completed_events for matches.' It also states a hard exclusion ('The page has no category or tag filter'), so an agent knows not to attempt topical filtering rather than discovering it at call time.

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