futpicks-mcp

Evaluate a Match

flab_evaluate_match

Read-onlyIdempotent

Score a match on demand to receive every market's pick with a full block breakdown. Provide a match ID to trigger the scoring engine.

Instructions

Score a match on demand through the scoring engine and return every market's pick with the full block breakdown. Requires Pro token.

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": {
      "matchId": "<matchId>"
    },
    "name": "flab_evaluate_match"
  }
}

Input Schema

Name	Required	Description	Default
`matchId`	Yes	Match ID (from flab_evaluate_matches)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Sep 6, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds valuable context beyond annotations: the Pro token requirement and the detailed return content (every market's pick and full block breakdown). No contradictions exist.

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?

Two sentences with no filler: the action is front-loaded, the output scope is concrete, and the access requirement is stated. Every sentence contributes useful information.

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 tool with strong annotations and no output schema, the description is largely complete: it states what is returned, the evaluation trigger, and the token requirement. It could be slightly stronger by explicitly routing to sibling tools for batch evaluation or alternative data views, but nothing critical is missing for correct invocation.

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?

The input schema has 100% description coverage and already explains matchId, including its source from flab_evaluate_matches. The tool description does not add parameter-level meaning, but with full schema coverage the baseline of 3 is appropriate.

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 states a specific verb and resource ('Score a match') and defines the exact output ('every market's pick with the full block breakdown'). The phrase 'on demand' and the singular 'a match' distinguish this tool from batch-oriented siblings like flab_evaluate_matches.

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 implies use for scoring a single match immediately, and explicitly notes the Pro token requirement. However, it does not name alternatives or state when not to use this tool versus flab_evaluate_matches, flab_match_details, or flab_pick_details.

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

Deploy Server