Skip to main content
Glama

Weekly Maps standings

weekly_standings
Read-only

The Weekly Maps table: for each of the 5 maps every live lineup with its record, confidence score, map score and whether it has enough battles to win the map, plus the overall weekly totals. Each map also names mostPoints (the main lineup with the highest mapScore so far this week, which is what wins the map) and inTheLead (the main lineup with the highest confidence right now, which may be catching up). Pass week (a past week id from past_weeks) for a finished week's final results.

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": "weekly_standings"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekNoOptional past week id, like "2026-11-08". Leave out for this week.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint annotation already covers safety, so the description earns credit for the payload semantics it adds: what mostPoints means (highest mapScore, wins the map) versus inTheLead (highest confidence, may be catching up), and the flag for whether a lineup has enough battles to win. However, nothing is said about freshness/refresh timing, size of the 5-map payload, or behavior for an invalid week id. Useful semantic gloss but no operational behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded block that describes the table first and the week parameter last, in the order a caller needs it. It is dense with parenthetical definitions but no sentence is filler. It is somewhat long for a single-parameter read tool, though every clause defines a returned field.

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?

With no output schema, the description carries the return-value burden and does so thoroughly, including the two named map-level fields a caller would otherwise misread. Only a single optional parameter is in play and it is fully explained. Missing only edge-case behavior (invalid week id, current-week partial data), which keeps it from a 5.

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?

Schema coverage is 100% and already documents the week parameter's format and optionality, so the baseline is 3. The description adds meaning beyond that by tying the value to a specific source (a past week id from past_weeks) and clarifying that omitting it yields the current week. That cross-reference is genuine added semantics.

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 names the resource concretely (the Weekly Maps table) and enumerates exactly what a caller gets back: every live lineup per map with record, confidence score, map score, and battle sufficiency, plus weekly totals. It distinguishes the result shape from a plain standings list by defining mostPoints and inTheLead. It lacks an explicit verb ("Returns/Gets") and never names the sibling tools it differs from, so it stops short of a 5.

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?

The only usage guidance is parameter-level: pass week for a finished week's final results, and obtain that id from past_weeks — a useful routing hint to a sibling. There is no statement of when to prefer this tool over weekly_winners, leaderboard, or get_week, and no exclusions or prerequisites are given. Usage is therefore implied rather than specified.

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