Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draftkings_pick6_rule_page

Retrieve public scoring and rule sections for a specified DraftKings Pick6 sport or format page by slug to review contest rules.

Instructions

DraftKings Pick6 sport-specific rules. Returns public scoring and rule sections for one supported Pick6 sport/format page. Discover supported slugs with draftkings_pick6_rules. This endpoint does not return player picks, projections, user entries, or location tokens.

Input Schema

NameRequiredDescriptionDefault
slugYesSport/format slug listed by draftkings_pick6_rules

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.3/5.0
Behavior4/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 disclose the important behavioral fact: this is public, read-only rule/scoring content and explicitly NOT player picks, projections, entries, or location tokens. That negative scoping prevents misuse. Remaining gap is the shape and size of the returned sections, but for static reference content the disclosure is adequate.

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

Conciseness4/5

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

Three short sentences, front-loaded with the purpose, followed by the discovery pointer and the exclusion list. Nothing is redundant, though the exclusion list is packed into one dense sentence.

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?

No output schema or annotations exist, so the description must stand alone; it covers what is returned, what is not returned, and how to obtain a valid slug. It could say more about how scoring and rule sections are organized in the response, but an agent could call it correctly as written.

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?

Schema coverage is 100% with an enum of slugs, so the baseline is 3; the description adds meaning by framing slug as a 'supported Pick6 sport/format page' and directing the agent to draftkings_pick6_rules for valid values. It does not explain format distinctions (e.g. pga-full-tournament vs pga-single-round, season-long variants), which the enum alone leaves implicit.

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 and resource: returns public scoring and rule sections for one Pick6 sport/format page. It scopes to a single slug and explicitly names the sibling draftkings_pick6_rules as the discovery step, so an agent can separate this from draftkings_pick6_sports or draftkings_pick6_rules without opening any schema.

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?

Gives clear routing: use draftkings_pick6_rules first to discover supported slugs, and the negative list (no picks, projections, user entries, location tokens) tells the agent when to look elsewhere. It stops short of naming the exact alternative tools for those excluded needs, so it is strong but not fully prescriptive.

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