Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draftkings_predictions_rules

Provides DraftKings Predictions rulebook and settlement-source links from the official rules page, helping you locate public rules without fetching market data or user context.

Instructions

DraftKings Predictions rules and settlement sources. Lists public rulebook and settlement-source links from the DraftKings Predictions Rules and Settlements page. It does not fetch market data, quotes, trades, user state, or location context.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.4/5.0
Behavior4/5

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

With zero annotations the description carries the full burden, and it does well: 'Lists public ... links' signals a read-only, unauthenticated, static listing, and the negative scope rules out mutation and live-data behavior. It stops short of describing pagination, counts, or link format, which is a modest gap.

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?

Three tight sentences, front-loaded with the resource and purpose, followed by the scope exclusion. No filler, and the differentiating constraint lands early.

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 zero-parameter tool with no output schema, the description adequately explains what comes back (rulebook and settlement-source links) and what it is not. Minor gaps remain around the shape/volume of the returned link list, but nothing blocks a correct call.

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

Parameters4/5

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

The tool takes no parameters, so per the baseline this scores a 4; the description correctly adds no parameter semantics because none exist, and there is nothing for the empty schema to explain.

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 (lists) and resource (public rulebook and settlement-source links) and is distinguished from the many DraftKings market/odds siblings by the explicit negative scope ('does not fetch market data, quotes, trades'). An agent can tell instantly this is a static reference/links tool, not a live market tool.

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 'does not fetch market data, quotes, trades, user state, or location context' clause effectively serves as a when-not statement that routes the agent toward this tool only for rules/settlement reference needs. There is no explicit positive 'use when' wording or named alternative, which keeps it short of 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

Other Tools