Skip to main content
Glama
Sign In
kenpom

kenpom

by omalleyandy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

kenpom_miscstats

Retrieve shooting percentages, block/steal rates, assist rates, and 3-point attempt rates for a given season, optionally filtered by team.

Instructions

Get miscellaneous stats: shooting percentages, block/steal rates, assist rates, 3-point attempt rates.

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": {
      "season": "<season>"
    },
    "name": "kenpom_miscstats"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoOptional: Filter to specific team name
seasonYesSeason year (e.g., 2025)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It lacks any mention of behavioral traits like read-only nature, data freshness, or authentication requirements. The verb 'Get' implies read-only, but this is not explicit.

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 a single, focused sentence that immediately states the purpose and lists example data. No unnecessary words or repetition.

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?

Given the simplicity (2 parameters, no nested objects), the description covers the basics but lacks details on output format or default behavior (e.g., returns data for one team or all teams per season). With no output schema, more context would help the agent.

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?

Input schema has 100% description coverage for both parameters (team and season). The tool description adds no additional meaning or constraints beyond the schema, resulting in a baseline score of 3.

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 clearly states the tool retrieves miscellaneous stats like shooting percentages and rates. However, it does not differentiate from sibling tools such as kenpom_fourfactors or kenpom_ratings, which may have overlapping stats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. The description merely lists what it does, without specifying contexts or prerequisites.

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

Deploy Server

Other Tools