Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

lolesports_teams

Read-only

Returns League of Legends esports teams with slug, code, status, home league and the full roster of players (summoner name, real name, role). Look up one team with slug such as t1 or search with q across name, code and slug; results are sorted by name and paged with page and limit up to 100. Filter status to active or archived.

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

Input Schema

NameRequiredDescriptionDefault
qNoOptional case-insensitive substring match against team name, code or slug.
hlNoOptional language code; defaults to en-US.
pageNoOptional 1-based page number; defaults to 1.
slugNoOptional exact team slug such as t1 or g2-esports. Takes precedence over q.
limitNoOptional page size from 1 to 100; defaults to 25.
statusNoOptional team status filter: active or archived.

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.2/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 safety profile is covered; the description adds real behavioral detail beyond that: results are sorted by name, paged via page/limit with a cap of 100, and status narrows to active or archived. It still does not say what happens on an empty match or whether the roster is always populated, which keeps it from 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?

Two sentences with no filler: the payload is front-loaded, then the query modes, sort order, paging and status filter follow in a single compact clause chain. Every clause carries operational information.

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?

An output schema exists, so return values need not be explained, yet the description still names the key fields. All 6 params are optional and fully schema-documented; the only omission in the prose is the hl language parameter, which the schema covers. Adequate for a filtered-list 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 description coverage is 100%, so the schema already documents every parameter including defaults and the slug-over-q precedence. The description restates those same semantics with a concrete slug example ('t1'), adding little beyond what the schema says. Baseline 3 applies when the schema does the heavy lifting.

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 teams') and enumerates the returned fields (slug, code, status, home league, full roster with summoner name, real name, role). This is clearly distinguishable from the sibling lolesports_leagues, lolesports_tournaments and lolesports_standings by resource.

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?

Gives two concrete invocation modes: single-team lookup via slug ('t1') and cross-field search via q over name, code and slug. It does not name an alternative tool or state when NOT to use this one, so it stops short of a full when/when-not statement.

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