Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lolesports_teams

Look up League of Legends Esports teams and rosters by slug or search query, filter by active or archived status, and retrieve player roles with paged results.

Instructions

League of Legends Esports teams and rosters. Returns teams with slug, code, status (active, archived), home league and the roster of players (summoner name, real name, role top, jungle, mid, bottom, support). Look up one team with slug or search with q; results are sorted by name and paged. The slug of every team is available from lolesports-standings and lolesports-schedule.

Input Schema

NameRequiredDescriptionDefault
qNoCase-insensitive substring of team name, code or slug
hlNoLanguage for names and labels; one of cs-CZ, de-DE, en-US, es-ES, es-MX, fr-FR, hu-HU, ja-JP, ko-KR, pl-PL, pt-BR, th-TH, tr-TR, vi-VN, zh-TW; defaults to en-US
pageNo1-based page number; defaults to 1
slugNoExact team slug such as t1 or g2-esports; takes precedence over q
limitNoPage size 1 to 100; defaults to 25
statusNoTeam status filter: active or archived

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, the description carries the full load and does disclose result shape (fields returned, roster composition), ordering (sorted by name), and pagination. It does not mention auth requirements, rate limits, or error behaviour for an unknown slug, which is the main remaining gap for a zero-annotation tool.

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 sentences, front-loaded with the returned resource, then access modes, then pagination, then the cross-reference for slugs. Every clause carries information an agent needs and none restates 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?

With no output schema, the description compensates by naming the returned fields, and it covers paging and sorting for a 6-parameter, all-optional tool. Minor omissions such as whether the roster includes inactive players or what 'home league' resolves to keep it from a 5.

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 every parameter including `q`, `hl`, `page`, `limit`, `slug`, and `status` is already documented with defaults and enum values. The description adds only the slug-over-q precedence, which the schema also states, so it does not meaningfully exceed the baseline.

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 resource (League of Legends Esports teams and rosters) and enumerates what comes back: slug, code, status, home league, and a roster with summoner name, real name, and role. The role and status enums are spelled out, so an agent immediately knows this is the team/roster lookup rather than a standings or schedule tool.

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?

Explicitly routes the two access modes: exact single-team lookup via `slug`, broad discovery via `q`. It also points to lolesports-standings and lolesports-schedule as the place to obtain slugs, which removes the usual discovery dead-end. No explicit when-not-to-use or exclusion clause, so it falls short of a 5.

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