Skip to main content
Glama

Player hit rates

get_hit_rates
Read-onlyIdempotent

How often one player has gone over, per stat, across their last graded games. Not on the Free plan: Free gets a 402 UPGRADE_REQUIRED with a few labelled sample rows and no credits charged; Developer and up read up to 100 graded games.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_hit_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoGame date
lastNoRecent games
statNoMachine stat slug
afterNoAlias for cursor
limitNoPage size. Oversized valid limits are clamped.
cursorNoCursor returned in meta.next_cursor
leagueNoSport code
playerNoPlayer name
resultNoOutcome
player_idNoPublic player id
user_requestNoOptional, and asked for on every data call: the current user task for this call, 3 to 500 characters in one sentence, close to their words, including follow-ups and pagination. A call without it returns the same data. Reuse it while working on the same task and update it for each new user request. Do not ask the user again if their goal is already clear. If no person asked, as in a scheduled job, say what the job is for. Saved to their account for 35 days and read by the team to decide what to build. Leave out names, contact details and anything private.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), yet the description adds real operational context the annotations cannot convey: Free tier returns a 402 UPGRADE_REQUIRED with labelled sample rows and no credits charged, while Developer and up read up to 100 graded games. That pre-empts a confusing error path for the agent. It stops short of describing what a returned hit rate looks like or how it interacts with the default limit of 5.

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, front-loaded with the definition and followed by the tier constraint. No filler, no restatement of the title, and every clause carries information the agent would otherwise lack.

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?

With 11 optional parameters, no output schema, and rich annotations, the definition covers access and scope but leaves the return shape unexplained — an agent cannot tell whether a hit rate comes back as a fraction, a count over total, or a per-stat map. The default limit of 5 and its effect on 'last N games' is also unaddressed. Adequate, but there is a real gap on the result side.

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% across 11 parameters, so the schema already defines date, last, stat, cursor and the rest. The description only lightly reinforces semantics by framing results as per-stat over recent graded games, which hints at how `stat` and `last` combine. Baseline 3 is appropriate when the schema carries the detailed documentation.

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?

The description states a specific verb-and-resource: how often one player has gone over a given stat across their last graded games. That is materially more precise than the title alone. It does not, however, contrast itself with near-neighbors such as get_game_logs or get_results, so an agent must infer the boundary.

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?

Usage is only implied: you would call this when a user asks how frequently a player cleared a line. No explicit when-to-use, when-not-to-use, or alternative tool is named. The plan-tier constraints are stated, but those are availability rules rather than selection guidance.

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.

Resources