Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_tournament_mvps

Fetch esports tournament MVP awards from BO3.gg newest first, optionally filtered by game, including award type, tournament, player, team, and source article.

Instructions

BO3.gg esports tournament MVPs. Returns the tournament most-valuable-player awards BO3.gg publishes, newest first, optionally for one game: the award type, tournament, player, team and the BO3 article about it. Every row seen has the type mvp.

Input Schema

NameRequiredDescriptionDefault
gameNoGame; one of cs2, valorant, lol, dota2, r6siege, mlbb; defaults to every game
limitNoPage size, 1 to 100; defaults to 20
offsetNoZero-based offset; defaults to 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description provides useful behavioral context: results are newest first, fields include award type, tournament, player, team, and article, and every row has type `mvp`. It does not describe pagination behavior or any access constraints, but the read-only list nature is clear from 'Returns'.

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 compact and front-loaded: it names the resource, then the return shape, then the optional filter. Every sentence adds useful information without repetition.

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?

For a simple list tool with fully described parameters and no output schema, the description gives enough detail about returned fields and ordering for an agent to call it correctly. Pagination defaults are already covered by the schema.

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 enum, limit, and offset are already documented. The description reinforces the optional game filter but adds no extra semantics for limit or offset, which is the expected baseline 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?

The description states a specific resource and action: returning tournament MVP awards from BO3.gg. It clearly scopes the result to MVP award rows, which distinguishes it from broader tournament or team siblings even without naming them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'optionally for one game' gives some usage context for the game filter, implying the tool can be used globally or narrowed to a single game. However, it does not specify when to choose this over related tournament tools or any exclusions.

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