Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lolesports_news

Retrieve League of Legends Esports news articles with titles, summaries, links, publication times, images, and authors; set language and result count.

Instructions

League of Legends Esports news. Returns the articles listed on the League of Legends Esports news page: title, summary, link, publication time, banner image, authors and whether the item links out to another site (a video or a store page). The page shows up to the newest 100 items and has no category, tag or paging controls; hl selects the site language and limit keeps the newest items only.

Input Schema

NameRequiredDescriptionDefault
hlNoSite language; one of cs-CZ, de-DE, el-GR, en-AU, en-GB, en-PH, en-SG, en-US, 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; defaults to en-US
limitNoNumber of newest articles to return, 1 to 100; defaults to all the page lists

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the up-to-100-item ceiling, the absence of category/tag/paging controls, the returned field set, and the non-obvious fact that some items link out to a video or store page instead of an article. It stops short of stating read-only/fetch semantics explicitly or any rate-limit behaviour.

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?

Three tight sentences: what it returns, what the payload looks like, then the constraints and parameters. The limiting facts (100 items, no categories/paging) are placed before the parameter notes the agent needs to act on, with no redundant restatement of the tool name.

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?

For a two-parameter read tool with no output schema, the description supplies the return shape, the ceiling and the filtering limitation, which is essentially everything needed to call it. The only small gap is that the mutation-free, fetch-only nature is implied by 'Returns' rather than stated outright in the absence of annotations.

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, but the description still adds meaning by tying `hl` to the site language and `limit` to 'the newest items only', which tells the agent the list is ordered newest-first and that truncation happens at the tail. The 24-value enum and the 1-100 bound remain schema-only, which is appropriate.

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 articles listed on the League of Legends Esports news page') plus the exact fields returned, so it is unmistakable against the other lolesports_* tools, which all deal with schedules, standings, teams or match data rather than editorial news.

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

Usage Guidelines3/5

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

Usage is only implied: the reader infers this is the news-fetch tool and that filtering/paging is unavailable, but the description never says when to pick it or names any alternative to use instead. For agents that might reach for schedule or live tools to find news, an explicit 'no search, use limit/hl only' routing note would help.

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