Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

gosugamers_encounters

Find other recorded GosuGamers head-to-head meetings between two teams from a match ID, excluding that match, to review prior tournament results, scores, winners, and match URLs.

Instructions

GosuGamers head-to-head meetings. Returns the other recorded meetings between two GosuGamers teams as seen from one match: tournament, start time, both teams with ids, tags and final scores, winner flags and the match URL. The given match_id itself is left out; game is required by the upstream but does not narrow the list. Take the ids from gosugamers-matches, gosugamers-results or gosugamers-rankings. Two teams with no other meeting return an empty list.

Input Schema

NameRequiredDescriptionDefault
gameYesGame section of the match; one of dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire, battlegrounds-mobile-india
match_idYesNumeric id of the match whose other meetings are wanted; that match is left out
team1_idYesNumeric id of the first team
team2_idYesNumeric id of the second team

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it describes the returned fields, the exclusion of match_id, the required-but-non-filtering game parameter, and empty-list behavior. It does not cover error or rate-limit behavior, but the core operational semantics are disclosed.

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?

The description is front-loaded and efficient: it states the core result, describes the return shape, notes parameter sourcing and the match_id exclusion, and ends with the empty-list edge case. No sentence 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, but the description explains what a result contains and what behavior to expect, including the empty-list case. For a read-only lookup tool with fully described input parameters, this is complete enough for an agent to call it correctly.

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 description coverage is 100%, so the schema already documents the parameters. The description still adds meaningful context by explaining that match_id is omitted from results and that game is required by the upstream but does not narrow the list.

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 other recorded head-to-head meetings between two teams from a given match. It clearly distinguishes the result from the match itself and from other GosuGamers endpoints by naming the exact scope and returned fields.

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?

Tells the agent to obtain team ids from gosugamers-matches, gosugamers-results, or gosugamers-rankings, and clarifies that the given match_id is excluded. It also notes the edge case of an empty list when no other meetings exist, though it does not explicitly name an alternative tool for a different scope.

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