futpicks-mcp

Get Picks Board

flab_picks_board

Read-onlyIdempotent

Retrieve a full football picks board for any date and filter by edge, odds, rating, league, market, lineup status, or preview inclusion to identify high-confidence model picks.

Instructions

Full picks board for a date with rich filters: edge/odds/data-quality ranges, lineup-confirmed flag, and preview inclusion. Public — no auth.

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": "flab_picks_board"
  }
}

Input Schema

Name	Required	Description
`date`	No	Date YYYY-MM-DD (default: today UTC)
`league`	No	Filter by league name
`market`	No	Filter by market
`rating`	No	Filter by rating
`maxEdge`	No	Maximum edge
`maxOdds`	No	Maximum decimal odds
`minEdge`	No	Minimum edge (e.g. 0.02)
`minOdds`	No	Minimum decimal odds
`includePreview`	No	Include T-3h preview picks (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Sep 6, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context with 'Public — no auth' and the notion of a 'full' board, but it does not disclose output shape, pagination, defaults beyond the schema, or why some described filters are absent from the schema.

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 description is compact and front-loaded with the core purpose. However, the second half lists filters that mismatch the schema, so not every statement earns its place; a cleaner version would either align the filter list with the actual schema or omit detail.

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

Completeness3/5

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

With 9 optional parameters, no output schema, and many sibling tools, the description gives a reasonable high-level picture but does not fully equip an agent to know what the response looks like or when this board is preferred over related picks tools. The auth disclosure helps, but overall completeness is only adequate.

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 and the description does not need to explain every parameter. The description adds some filter-range semantics for edge/odds and preview inclusion, but also references 'data-quality ranges' and a 'lineup-confirmed flag' that have no corresponding schema parameters, so it provides no clear added value.

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?

The description clearly identifies a specific resource and scope: 'Full picks board for a date.' However, it does not differentiate the tool from siblings like flab_picks_today, flab_picks_history, or flab_pick_details, and it mentions filters such as 'lineup-confirmed flag' and 'data-quality ranges' that are not present in the input schema, which slightly muddies the intended capability.

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 phrase 'for a date' implies this is the date-scoped board tool, giving some usage context. But there is no explicit guidance on when to use this versus flab_picks_today, flab_picks_history, or flab_pick_details, and no exclusions or alternative routing are provided.

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

Deploy Server