Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_transfers

Fetch BO3.gg esports player and coach transfer feeds, newest first, with paging and filters for team, player, action, and role; each row includes its game.

Instructions

BO3.gg esports transfer feed. Returns BO3.gg's esports player and coach transfer feed, newest first by default, with paging and filters: team_id (moves into or out of one team), player_id, action (join, change, leave) and role (player, coach). The feed cannot be filtered by game upstream, so every row carries its game instead; narrow it with a team or player id.

Input Schema

NameRequiredDescriptionDefault
roleNoRole; one of player, coach
sortNoOrder by date; one of newest, oldest; defaults to newest
limitNoPage size, 1 to 100; defaults to 20
actionNoTransfer action; one of join, change, leave
offsetNoZero-based offset; defaults to 0
team_idNoBO3 team id; transfers into or out of this team
player_idNoBO3 player id; this person's transfers

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 usefully discloses that this is a read-style feed, defaults to newest first, supports paging and filters, and has an upstream limitation: game cannot be filtered but appears on each row. It does not discuss auth, rate limits, or side effects, but it adds meaningful behavioral context beyond the schema.

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 with a clear one-line summary, then adds filters and one important limitation. Every sentence contributes useful information without repetition or filler.

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?

For a paginated feed tool with no output schema, the description covers defaults, filters, paging, and the key game-filtering limitation well enough to call it correctly. It could say more about the shape of returned rows beyond the fact that each row carries game, but no critical invocation detail is missing.

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 all seven parameters, including enums and defaults. The description restates the key filters and adds a useful narrowing recommendation, but it does not add format or semantic detail beyond what the schema provides.

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 verb and resource: it returns BO3.gg's esports player and coach transfer feed. It also names the source, default ordering, paging, and filters, making it easy to distinguish from match, team, or player detail tools.

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?

It explains the operational context well: use filters for team, player, action, and role, and narrow the feed with team_id or player_id because game cannot be filtered upstream. It does not name an alternative sibling tool or state when not to use this feed, so it falls short of explicit routing guidance.

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