Skip to main content
Glama
Sign In
kenpom

kenpom

by omalleyandy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

kenpom_pointdist

Retrieve point distribution percentages from free throws, two-pointers, and three-pointers for offensive and defensive efficiency. Filter by team and season.

Instructions

Get point distribution data: percentage of points from FTs, 2-pointers, and 3-pointers for offense and defense.

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_pointdist"
  }
}

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.2/5.0
Behavior2/5

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

No annotations are provided, so description carries full burden. It only states what data is returned but does not disclose behavioral traits such as data freshness, authentication requirements, rate limits, or whether the data is aggregated or per-game.

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?

Single sentence with no wasted words. It is front-loaded with the main action and quickly provides specific details about the data returned.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is present, so description should compensate by describing return structure. It mentions metrics but not how they are organized (e.g., separate for offense/defense, team-level). For a tool with 2 parameters and no output schema, the description is 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 100%, meaning the schema already documents both parameters. The description adds no additional meaning beyond what the schema provides; it does not elaborate on parameter usage or valid values.

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

Purpose5/5

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

Description clearly specifies verb 'Get', resource 'point distribution data', and details the metrics (percentage of points from FTs, 2-pointers, 3-pointers for offense and defense). It distinguishes from sibling tools by focusing uniquely on point distribution.

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 explicit guidance on when to use this tool versus alternatives like kenpom_fourfactors or kenpom_ratings. The description implies usage for point distribution queries but does not provide when-not-to-use or context-specific recommendations.

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