Skip to main content
Glama

In-game metrics

aura_metric_series
Read-onlyIdempotent

Time series of in-game metrics for one game, such as win probability, score margin and player lines. Call without definitionId first to see which series exist.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "gameId": "<gameId>"
    },
    "name": "aura_metric_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNopage.nextCursor from the previous call
gameIdYesAura game id from aura_list_games or aura_live_games
entityIdNoTeam or player id
pageSizeNoDefaults to 500
definitionIdNoSeries id from a call without it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"page.nextCursor from the previous call"
    • removedInput schema / properties / limit
      Removed value: -{
      -  "maximum": 500,
      -  "minimum": 1,
      -  "type": "number"
      -}
    • addedInput schema / properties / pageSize
      Added value: +{
      +  "description": "Defaults to 500",
      +  "maximum": 500,
      +  "minimum": 1,
      +  "type": "number"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds the discovery-first calling pattern, which is genuinely useful behavior, but says nothing about time range, ordering, or how large a series can be.

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?

Two sentences, zero filler, with the resource identity front-loaded and the prerequisite calling pattern immediately after.

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 read-only, paginated series tool with full schema coverage and no output schema, most of what an agent needs is present. The notable gap is the time dimension: no hint about the window covered, granularity, or sort order of the returned series.

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 coverage is 100%, so all five parameters are already documented, including definitionId as "Series id from a call without it." The description reinforces definitionId's optionality but adds no new meaning for entityId, cursor, or pageSize.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: a time series of in-game metrics scoped to one game, with concrete examples (win probability, score margin, player lines). That distinguishes it from snapshot-style siblings like aura_boxscore or aura_get_game, though it never names those siblings explicitly.

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?

"Call without definitionId first to see which series exist" gives a concrete two-step discovery workflow an agent must follow to get usable results. It stops short of naming an alternative tool or stating when-not to use this one.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.