Skip to main content
Glama
gsypolt

MFL MCP Server

by gsypolt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get MFL fantasy points for players

mfl_get_player_scores
Read-onlyIdempotent

Retrieve fantasy points under your league's scoring rules for a week, season total, or average, filtered by franchise, player, or position.

Instructions

Get fantasy points under the league's scoring rules for a week, year-to-date total, or season average. Filter to a franchise's roster, specific players, or a position.

Args:

  • period ('week' | 'ytd' | 'avg'): default 'ytd'. With 'week', pass week.

  • week (number, optional): used when period='week'. Omit for the current week.

  • franchise (string, optional): "mine", a franchise ID, or a team name to score only that roster.

  • player_ids (string, optional): comma list of MFL player IDs (use mfl_get_players to find IDs).

  • position (string, optional): e.g. "LB".

  • league, season: optional.

  • limit (1-200, default 25), offset (default 0).

  • response_format: 'markdown' (default) or 'json'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
weekNoNFL week number (1-22). Omit for the current week.
limitNoMax results to return (1-200, default 25).
leagueNoWhich league: a configured alias (see mfl_list_leagues), league name, or numeric MFL league ID. Omit for the default league.
offsetNoResults to skip, for paging (default 0).
periodNo'week', 'ytd' (default), or 'avg'.ytd
seasonNoSeason year, e.g. 2025 for last season. Omit for the league's default (usually current) season.
positionNoOne position, e.g. "RB".
franchiseNo"mine", a franchise ID, or a team name.
player_idsNoComma list of MFL player IDs.
response_formatNo'markdown' for readable output (default) or 'json' for structured data.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is fully covered. The description adds the default period (ytd), default limit (25), and the ID-lookup cross-reference, but discloses nothing about result ordering, pagination behavior, or scoring-rule edge cases.

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?

Front-loaded one-sentence purpose followed by a compact Args list; no filler sentences. The Args block is somewhat redundant with the 100%-covered schema but remains scannable and each line maps to a real parameter.

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

Completeness5/5

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

For a 10-parameter, all-optional read tool with a full input schema, no output schema, and complete annotations, the description supplies everything needed to invoke it correctly, including period/week coupling and the default response format.

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%, so the schema already documents all 10 parameters, and the Args block largely restates it. The only added value beyond the schema is the cross-reference to mfl_get_players for player IDs and the 'mine' shorthand for franchise, which is marginal.

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 specific verb (Get) plus resource (fantasy points under the league's scoring rules) and the three temporal scopes (week/ytd/avg). It does not differentiate itself from siblings like mfl_get_live_scoring, so an agent must infer the boundary, but the purpose itself is unambiguous.

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?

The description lists filtering options (franchise, players, position) and notes mfl_get_players for ID lookup, which implies usage. However it never states when to prefer this over mfl_get_live_scoring or mfl_get_roster, and gives no explicit when-not conditions.

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