v12-dfs

betting_cross_book

Cross Book

Cross-book value: FanDuel vs DraftKings (DK pulled via ESPN's public API, no key/WS). LINE_SHOP (the books hang different numbers — take the easier side) and PRICE_SHOP (better price, same line) are CONFIRMED edges, no model needed. Arbitrage is NOT auto-reported (needs over/under sides, which ESPN doesn't label). Overnight only pitcher_strikeouts overlaps; richer markets appear near game time.

Responses:

200: Successful Response (Success Response) Content-Type: application/json 422: Validation Error Content-Type: application/json

Example Response:

{
  "detail": [
    {
      "loc": [],
      "msg": "Message",
      "type": "Error Type",
      "ctx": {}
    }
  ]
}

Input Schema

TableJSON Schema

Name	Required	Description	Default
`prop`	No		pitcher_strikeouts

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 17, 2026

TDQS

D1.5/5.0

Behavior1/5

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

With no annotations provided, the description must fully convey behavioral traits. It does not explain what the tool returns, whether it performs side effects, requires authentication, or has rate limits. It mentions 'CONFIRMED edges' and 'no model needed' but does not describe the actual behavior or output of the tool.

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

Conciseness2/5

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

The description includes unnecessary boilerplate about HTTP status codes and an example validation error, which inflates length without adding value for an AI agent. The first sentence 'Cross Book' is not informative. The description is unstructured and does not front-load key information.

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

Completeness1/5

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

Given no output schema and no annotations, the description is incomplete. It does not explain what the tool returns, how to interpret the cross-book value, or how to use the response. The mention of 'LINE_SHOP' and 'PRICE_SHOP' is unexplained, leaving the agent without necessary context to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not explain the single parameter 'prop' (default 'pitcher_strikeouts'). The description mentions 'pitcher_strikeouts' in context but does not clarify that it is the parameter, nor what values it accepts or how it affects results. The parameter is left completely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Cross Book' and mentions 'cross-book value' but lacks a clear verb indicating what the tool does (e.g., 'get', 'calculate', 'list'). It implies it provides information about edges between books but the action is ambiguous. The title is null and the description does not specify a distinct resource or operation.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus its many betting-related siblings like betting_scan_edges or betting_best_bets. It mentions arbitrage is not auto-reported but fails to clarify scenarios where cross-book is preferred. No exclusions or alternatives are provided.

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

All v12-dfs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?