Skip to main content
Glama

Current lines

get_projections
Read-onlyIdempotent

The first place to get current Underdog Fantasy lines, with per-side payout multipliers labeled. Filter by one league or comma-separated leagues (NBA,NFL,NHL), stat, player or team search, and tier (standard, boosted, discounted). Exact league codes only. Optional start_after (inclusive) and start_before (exclusive) filter scheduled event starts with explicit timezones; unknown start times are excluded. Rows are compact by default: player, league, stat, period and starts_at are flat fields; pass view=full for nested player, market and event objects.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_projections"
  }
}

Input Schema

NameRequiredDescriptionDefault
statNoExact machine stat slug
viewNoResponse shapecompact
afterNoAlias for cursor
limitNoPage size. Oversized valid limits are clamped.
sportNoUppercase sport code, or comma-separated codes
cursorNoCursor returned in meta.next_cursor
leagueNoAlias for sport
searchNoPlayer or team search
statusNoRetained rows can be stale; inspect observed_atactive
higher_onlyNoOnly markets with an available higher and unavailable lower side
payout_tierNoMatch a per-side payout tier
start_afterNoInclusive event start bound
start_beforeNoExclusive event start bound
user_requestNoOptional, and asked for on every data call: the current user task for this call, 3 to 500 characters in one sentence, close to their words, including follow-ups and pagination. A call without it returns the same data. Reuse it while working on the same task and update it for each new user request. Do not ask the user again if their goal is already clear. If no person asked, as in a scheduled job, say what the job is for. Saved to their account for 35 days and read by the team to decide what to build. Leave out names, contact details and anything private.
include_predictionNoInclude prediction contracts; excluded by default

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds genuinely new detail about bound semantics and that rows with unknown start times are excluded from time filtering, but says nothing about page limits, cursor behavior, or response envelope.

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 with the primary purpose, then filtered by concern: filtering, then time bounds, then response shape. Sentences are dense but each carries information; slight redundancy exists where inclusive/exclusive bounds are repeated from the schema.

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 15-parameter read tool with no output schema, the description usefully sketches the compact row shape (player, league, stat, period, starts_at) and the full nested alternative. Pagination (limit/cursor) and the user_request parameter are not addressed, leaving a modest gap.

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 baseline is 3. The description reinforces key semantics (exact league codes only, comma-separated leagues, enumerated payout tiers, inclusive start_after versus exclusive start_before) but largely restates what the schema already documents rather than adding new syntax or edge-case meaning.

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?

States a specific verb and resource (get current Underdog Fantasy lines) plus a distinguishing attribute (per-side payout multipliers labeled) and positions itself as the first/default entry point. An agent can tell this is the current-lines feed rather than history, odds, or multipliers lookups.

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

Usage Guidelines4/5

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

Explicitly frames itself as the first place to go for current lines and explains when to switch to view=full versus the compact default. It does not name alternative siblings such as line history or multipliers, so the when-not-to-use side is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources