Skip to main content
Glama

LUMA NBA Impact Metrics

wowy

Read-onlyIdempotent

With-or-without-you for teammates in a team-season: team ratings with both on, only A, only B, neither. Give two players, or one player to list his partners. No possession minimum: check poss_together (small states are noise).

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": {
      "player": "<player>"
    },
    "name": "wowy"
  }
}

Input Schema

NameRequiredDescriptionDefault
withNo
limitNo
playerYes
seasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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), so the description's job is to add analytic context — and it does: there is no possession minimum applied, and the returned poss_together column should be inspected because small samples are noise. That is genuine, decision-relevant behavior disclosure beyond the annotations.

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?

Three compact sentences, front-loaded with the core operation before the input modes and the statistical caveat. Dense with useful content and no filler, though the shorthand style ('both on, only A, only B, neither') requires careful reading.

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?

There is no output schema, so the description bears some burden for explaining results; it hints at a poss_together column but never describes the rating fields or response shape. The four-condition framing is adequate for calling the tool, but the return side and the undocumented limit parameter leave it incomplete.

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 0%, so the description must carry all four parameters. It conveys the player/with duality ('give two players, or one player') and implies season via 'team-season', but the limit parameter is never mentioned and 'with'/'season' are not named explicitly, leaving real gaps.

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 spells out the cryptic name: it computes with-or-without-you team ratings for a teammate pairing across four states (both on, only A, only B, neither) within a team-season. That is a specific analytic resource, and the two-player vs one-player modes frame it differently from siblings like onoff or compare, though it does not explicitly name them.

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?

It gives clear input-mode guidance: pass two players for a pairing, or one player to list his partners. However, it never states when to prefer this over onoff or compare, so the agent must infer the boundary between overlapping analytic tools.

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