Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gosugamers_team_results

Fetch a GosuGamers team's completed matches, newest first, including tournament, scores, winners, and match URLs, with page and page_size controls.

Instructions

GosuGamers team match history. Returns the completed matches of one GosuGamers team, newest first, across the games it plays: start time, tournament, both teams with ids and final scores, winner flags and the match URL. Paged with page and page_size (up to 100, default 10); total_rows is the team's full history. An unknown team id returns an empty list. Take team_id from gosugamers-rankings, gosugamers-results or gosugamers-team.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page; defaults to 1
team_idYesNumeric team id from gosugamers-rankings, gosugamers-results or gosugamers-team
page_sizeNoPage size, 1 to 100; defaults to 10

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 burden and does well: it discloses ordering, the returned field set, pagination limits/defaults, that total_rows equals the team's full history, and that an unknown team id yields an empty list rather than an error. Missing only details like auth, rate limits or whether in-progress matches are excluded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

It is a dense but front-loaded block that leads with what is returned, then pagination, then edge-case behavior and id sourcing. Every sentence carries information; only the slight repetition of the schema's pagination details is redundant.

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?

There is no output schema, and the description compensates by enumerating the return fields, ordering, pagination contract and empty-result behavior. An agent has everything needed to call and interpret this tool correctly.

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 page, page_size and team_id are already documented with defaults and ranges. The description largely restates those and adds the total_rows note, which is a return field rather than a parameter, so it stays at 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 verb and resource ('Returns the completed matches of one GosuGamers team'), plus ordering (newest first) and the exact fields returned. This clearly separates it from siblings like gosugamers_results (global results) and gosugamers_team (team profile).

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?

The description tells the agent where to get team_id (gosugamers-rankings, gosugamers-results, gosugamers-team), which is actionable routing guidance. However, it never explicitly contrasts scope with gosugamers_results, so 'use this instead of X when...' is left implicit.

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