Skip to main content
Glama

get_rolling_odds

Retrieve Teamfight Tactics champion shop rolling probabilities by player level to calculate optimal reroll strategies and improve in-game decision making.

Instructions

Get TFT champion shop rolling odds by player level. Shows the probability of seeing each cost tier (1-5) at a given level. Omit the level to see the full table.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNoPlayer level (2-10). Omit to get the full table.

Implementation Reference

  • The getRollingOdds function implements the tool logic, returning rolling odds for a specific level or the full table.
    export function getRollingOdds(
      input: GetRollingOddsInputType,
    ): GetRollingOddsResult | GetRollingOddsError {
      if (input.level != null) {
        const odds = ROLLING_ODDS[input.level];
        if (!odds) {
          return { error: `Invalid level ${input.level}. Valid range is 2-10.` };
        }
        return { levels: [{ level: input.level, odds }] };
      }
    
      // Return full table
      const levels: LevelOdds[] = Object.entries(ROLLING_ODDS)
        .map(([lvl, odds]) => ({ level: Number(lvl), odds }))
        .sort((a, b) => a.level - b.level);
    
      return { levels };
    }
  • Zod schema defining the input for get_rolling_odds tool.
    export const GetRollingOddsInput = z.object({
      level: z
        .number()
        .min(2)
        .max(10)
        .optional()
        .describe('Player level (2-10). Omit to get the full table.'),
    });
  • src/server.ts:187-196 (registration)
    Registration and execution of the get_rolling_odds tool within the MCP server.
    // 8. get_rolling_odds
    server.tool(
      'get_rolling_odds',
      'Get TFT champion shop rolling odds by player level. Shows the probability of seeing each cost tier (1-5) at a given level. Omit the level to see the full table.',
      GetRollingOddsInput.shape,
      async (params) => {
        try {
          const result = getRollingOdds(params);
          return {
            content: [{ type: 'text' as const, text: formatGetRollingOdds(result) }],
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the tool's behavior (shows probability tables, returns full table when level omitted) but doesn't address error handling, data freshness, rate limits, or authentication requirements that would be important for a data retrieval tool.

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 perfectly concise with two sentences that each serve distinct purposes: the first states the core functionality, the second explains the parameter behavior. No wasted words, front-loaded with essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only tool with good schema coverage, the description is adequate but has gaps. Without annotations or output schema, it doesn't describe the return format (probability table structure), data units (percentages or decimals), or potential limitations. It's minimally viable but could provide more complete context.

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?

With 100% schema description coverage, the schema already documents the level parameter thoroughly. The description adds valuable context about what happens when the parameter is omitted ('Omit to get the full table'), which isn't captured in the schema. This elevates it above the baseline 3.

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 clearly states the tool's purpose with specific verb ('Get'), resource ('TFT champion shop rolling odds'), and scope ('by player level'). It distinguishes from siblings by focusing on probability tables rather than champion/item/trait data retrieval.

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?

The description provides clear context about when to use this tool (for probability data) and includes guidance about parameter omission behavior. However, it doesn't explicitly contrast with alternative tools or specify when not to use it versus siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gregario/tft-oracle'

If you have feedback or need assistance with the MCP directory API, please join our Discord server