Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bo3_economy_baseline

Retrieve site-wide CS2 round win rates for every buy-level pairing to establish an economy baseline for comparing a team's economy stats.

Instructions

BO3.gg CS2 economy baseline. Returns the site-wide CS2 round win rate for every pairing of buy levels (rounds, wins, win rate), the baseline to compare a team's economy view of bo3-team-stats with. Levels: -1 full eco, 0 semi-eco, 1 half buy, 2 full buy; the opposing level is null when it is unknown.

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Without annotations, the description carries the burden and does disclose the returned fields (rounds, wins, win rate) and the meaning of each buy level including null handling. It does not mention operational traits like caching, freshness, or rate limits, but it adequately explains the data semantics for a read-only reference endpoint.

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 the core purpose, then immediately covers the comparison use case and level definitions. Every sentence contributes 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?

With no input parameters and no output schema, the description provides enough detail to understand what is returned and how to interpret the buy-level pairings. It also connects the tool to the relevant sibling output (`economy` view), so an agent has what it needs 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?

There are zero parameters, so the baseline is 4. The description still adds useful domain semantics by defining buy-level values and the meaning of a null opposing level, which helps interpret the returned data even though no input schema exists.

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 uses a specific verb/resource phrase: 'Returns the site-wide CS2 round win rate for every pairing of buy levels.' It also explicitly distinguishes this tool as the baseline to compare against a team's `economy` view of `bo3-team-stats`, which is useful among many sibling BO3 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 states the comparison context clearly: use this baseline with a team's `economy` view from `bo3-team-stats`. It does not explicitly name when not to use it or mention other alternatives, but for a zero-parameter global baseline the intended usage is clear.

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