Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draftkings_pick6_rules

Retrieve public DraftKings Pick6 rule and scoring sections, including verified child-page detail routes, to review contest rules without player picks, projections, entries, or location tokens.

Instructions

DraftKings Pick6 rules. Returns public rule sections from the DraftKings Pick6 Rules and Scoring page plus child pages with verified detail routes. Unverified upstream links are omitted from the slug directory. It does not return player picks, projections, user entries, or location tokens.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully states that only public rule sections are returned, that child pages have verified detail routes, and that unverified upstream links are omitted. It still leaves out important behavioral context such as whether the operation is strictly read-only, the response shape, and any access constraints.

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?

The definition is short and front-loaded, with the main scope stated first and exclusions following. The opening 'DraftKings Pick6 rules' slightly restates the tool name, but the remaining sentences add useful substance without waste.

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

Completeness3/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 gives enough to understand the content domain and exclusions. However, it does not clarify the output structure of the rule sections or resolve overlap with the sibling draftkings_pick6_rule_page, so an agent still has some uncertainty about what exactly will be returned.

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 zero parameters and the schema is empty. The description is not expected to explain parameter usage, so the baseline score of 4 applies.

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

Purpose4/5

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

The description gives a specific resource (DraftKings Pick6 rules) and states exactly what it returns: public rule sections from the Pick6 Rules and Scoring page plus child pages with verified detail routes. It also clarifies what it does not return, which helps distinguish it from betting and projections tools, though it does not explicitly name the closely related sibling draftkings_pick6_rule_page.

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 negative scope is useful: it says it does not return player picks, projections, user entries, or location tokens, which tells the agent when not to use it. However, it does not name alternative tools for those excluded use cases or explain when to prefer this tool over draftkings_pick6_rule_page or draftkings_predictions_rules.

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