Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draftkings_pick6_sports

Returns a dated Help Center snapshot of Pick6 sports and contest formats, including exact sport codes, published links, and the CFB/CBB jurisdiction restriction.

Instructions

DraftKings Pick6 sport directory. Returns the dated public Help Center snapshot of Pick6 sports and contest formats, with exact sport codes and links published by the Help Center, plus the CFB/CBB jurisdiction restriction. Product-page reachability is not verified. This directory does not return picks or projections and does not imply availability in the caller's location.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses that the data is a dated public snapshot, that product-page reachability is unverified, that jurisdiction restrictions apply for CFB/CBB, and that it does not imply local availability. These are exactly the behavioral caveats an agent needs.

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 sentences, front-loaded with the core purpose and followed by precise limitations. Every sentence adds distinct value with no repetition.

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?

No output schema exists, so the description must explain return content. It clearly states the snapshot nature, what fields are included (sport codes, formats, links), and critical caveats. Complete for a simple zero-parameter directory.

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 has zero parameters, so the baseline is 4. The description adds useful context about what the directory contains but has no parameter semantics to clarify.

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 resource (DraftKings Pick6 sport directory) and exactly what it returns: dated Help Center snapshot, sport codes, contest formats, and links. It also explicitly rules out picks/projections, which distinguishes it from sibling prediction 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?

It gives clear context and negative guidance ('does not return picks or projections', 'does not imply availability'), but it never names an alternative sibling tool or states an explicit 'use this when...' condition. Usage is strongly implied rather than fully prescribed.

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