futpicks-mcp

Get Pick Details

flab_pick_details

Read-onlyIdempotent

Retrieve complete pick details by ID, including market, line, edge, score, rating, and scoring-block breakdown. Access specific picks directly with no authentication.

Instructions

Get full detail for a single pick by ID: market, line, edge, score, rating, and the scoring-block breakdown. Public — no auth.

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": {
      "id": "<id>"
    },
    "name": "flab_pick_details"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Pick ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Sep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, and the description adds the useful context that it is 'Public — no auth.' It also clarifies the specific detail content returned, providing value beyond the annotation hints.

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

Conciseness5/5

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

The description is a single sentence that front-loads the operation and resource, then lists the returned fields and the auth context. Every clause contributes useful information, with no unnecessary repetition of schema or annotation data.

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?

Given the single required parameter, full schema coverage, and strong safety annotations, the description supplies the remaining essential context: public access and the fields returned. There is no output schema, but the field enumeration gives an agent enough information to call and interpret the tool correctly.

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%, and the schema already explains 'id' as an integer 'Pick ID' with exclusiveMinimum 0. The description only repeats 'by ID,' adding no meaningful semantic information beyond what the schema provides.

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?

The description clearly states the verb 'Get' and the resource 'full detail for a single pick by ID,' then enumerates the returned fields: market, line, edge, score, rating, and scoring-block breakdown. This makes the tool's purpose specific and distinguishes it from list-oriented sibling tools.

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?

The description establishes a clear usage context: use this when you need comprehensive detail for one pick identified by an ID, rather than a list of picks. It does not explicitly name sibling alternatives or provide when-not conditions, which prevents a 5.

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

Deploy Server