Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

gosugamers_team_results

Read-only

Returns the completed matches of one GosuGamers esports team, newest first, across the games it plays: start time, tournament, both teams with ids and final scores, winner flags and match URL. Requires team_id (from gosugamers_rankings, gosugamers_results or gosugamers_team); page and page_size (up to 100) page through total_rows. An unknown team id returns an empty list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "team_id": "<team_id>"
    },
    "name": "gosugamers_team_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOptional 1-based page, default 1.
team_idYesRequired numeric team id from gosugamers_rankings, gosugamers_results or gosugamers_team.
page_sizeNoOptional page size 1 to 100, default 10.

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=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior that annotations don't: newest-first ordering, empty-list handling for an unknown team id, and that pagination walks total_rows. Rate limits or throttling are not mentioned, so not 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.

Conciseness4/5

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

Three sentences, front-loaded with the purpose and return shape, then the required parameter, then the edge case. The enumeration of returned fields is somewhat redundant given an output schema exists, but it is compact and not 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?

With an output schema present, the description needn't specify return shape, yet it still covers ordering, unknown-id behavior and pagination. An agent has everything needed to call it correctly and interpret an empty result.

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 documents page, team_id (including its sourcing) and page_size (1-100, default 10). The description largely restates those facts, adding no syntax or semantics beyond the schema, so the baseline 3 applies.

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 esports team'), scopes it to a single team and completed matches, and notes ordering (newest first) and cross-game coverage. The 'one team' scoping implicitly delineates it from the fleet-wide gosugamers_results sibling.

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 the required prerequisite (team_id) and explicitly names the three sibling tools that supply it, plus the pagination contract (page/page_size up to 100). It stops short of an explicit 'use X instead when you want all teams' routing statement, which keeps it at 4 rather than 5.

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