Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draftkings_dfs_guide

Retrieve public DraftKings Daily Fantasy contest-type summaries and sport landing-page links to research DFS guide categories.

Instructions

DraftKings Daily Fantasy guide. Returns public contest-type summaries and sport landing-page links from DraftKings' Daily Fantasy Sports guide. Use draftkings_dfs_glossary for the page's public terminology definitions. This is a read-only guide directory; it does not access contests, lineups, player pools, or accounts. Availability and age limits vary by location.

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 no annotations, the description carries the full burden and does well: it declares read-only behavior, enumerates what data it does NOT touch (contests, lineups, player pools, accounts), and warns that availability and age limits vary by location. It stops short of describing response shape or pagination.

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?

Four short sentences, each earning its place: what it returns, the sibling alternative, the scope exclusions, and the availability caveat. The core value proposition is front-loaded in sentence one.

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 read tool with no output schema and no annotations, the description covers the essentials: content of the response, boundaries, and the closest alternative. Only the concrete shape of the returned guide directory is left implicit, which is minor.

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, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a no-argument directory call.

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 contest-type summaries and sport landing-page links') from a named source, and explicitly distinguishes itself from the glossary sibling. An agent can tell what this tool yields without opening anything else.

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?

Explicitly routes terminology questions to draftkings_dfs_glossary and clarifies that contests, lineups, player pools, and accounts are out of scope, which steers the agent toward other draftkings_* tools. It lacks a positive 'use this when you need X' trigger, so it falls just 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