Token Bowl MCP Server

get_user

Retrieve a Sleeper user's profile, including ID, username, display name, avatar, and account creation date, by their username or numeric user ID.

Instructions

Get detailed information about a Sleeper user by username or user ID.

Args: username_or_id: Either the unique username or user_id of the Sleeper user. Cannot be empty. Will be converted to string.

Returns user profile including:

User ID (unique numeric identifier)
Username (unique handle)
Display name (shown in leagues)
Avatar ID for profile picture
Account creation date

Example: get_user("JohnDoe123") or get_user("123456789")

Returns: Dict containing user profile information

Input Schema

TableJSON Schema

Name	Required	Description	Default
`username_or_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the field-level return contents and reinforces the non-empty constraint, but says nothing about permissions, error behavior for unknown users, or rate limits.

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

Conciseness3/5

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

The useful routing sentence is front-loaded, but the args block duplicates the example line and the Returns section restates the field list. Several lines don't earn their place.

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?

For a single-parameter lookup with an output schema present, the description is largely complete: it defines the input contract and the returned profile shape, needing only usage routing.

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 0%, so the description must compensate. It explains that the single parameter accepts either a username or a numeric ID, is converted to string, and cannot be empty, plus two examples. This meaningfully exceeds the bare schema.

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?

States a clear verb (get) and resource (user profile) for Sleeper. Distinguishes from sibling get_league_users, which is league-scoped, and token_bowl_chat_get_user_profile by being platform-specific, though it doesn't explicitly call out these distinctions.

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 versus alternatives like get_league_users or search_players_by_name. The 'Cannot be empty' note is a parameter constraint, not usage guidance. An agent gets no help choosing this tool.

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

Deploy Server