Skip to main content
Glama
Sign In
kenpom

kenpom

by omalleyandy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

kenpom_top_teams

Retrieve the top N college basketball teams ranked by a selected efficiency metric such as Adjusted Efficiency Margin, Offensive Efficiency, or SOS.

Instructions

Get top N teams by a specific metric (AdjEM, AdjOE, AdjDE, etc.)

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": {
      "metric": "<metric>"
    },
    "name": "kenpom_top_teams"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of teams to return (default: 25)
metricYesMetric to rank by: AdjEM, AdjOE, AdjDE, AdjTempo, SOS
seasonNoSeason year (default: current)

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 must disclose behavioral traits. It only states the basic operation without mentioning data source, freshness, pagination, error conditions, or whether the order is descending. Minimal disclosure.

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?

The description is a single, clear sentence with no extraneous words. It is front-loaded with the core action. However, it sacrifices information for brevity.

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 exists, but the description does not explain the return format, units, or what fields are included. For a tool without output schema, this is insufficient for an agent to understand the result.

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 coverage is 100%, so the description adds little beyond what the enum and parameter descriptions already provide. The description merely echoes the enum values without additional context or usage hints.

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 states the action: get top N teams by a specific metric. It lists example metrics (AdjEM, AdjOE, AdjDE, etc.), which distinguishes it from sibling tools that return all teams or different data.

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_ratings or kenpom_teams. The description implies it's for top teams, but does not specify prerequisites, exclusions, or comparison with siblings.

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