Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draftkings_dfs_sports

Retrieve the public DraftKings daily fantasy US sport catalog with exact sport codes and enabled/public-contests flags; flags reflect the source catalog, not caller location eligibility.

Instructions

DraftKings Daily Fantasy sports catalog. Returns the public US-DK sport catalog with exact sport codes and DraftKings' enabled/public-contests flags. The flags describe the source catalog, not caller-specific location eligibility. This endpoint does not access contests, lineups, prizes, or account data.

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 burden and does well: it discloses that the catalog is public, that flags describe the source catalog rather than caller-specific location eligibility, and that no account or contest data is touched. It stops short of stating authentication needs or whether the catalog is static versus refreshed per request.

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, front-loaded with what is returned, then the flag caveat, then the scope exclusion. Every sentence adds new information; none restates the name.

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?

With no input schema, no annotations, and no output schema, the description must define the payload and does: catalog of sports, exact sport codes, and two flags with their interpretation. It could have sketched the response shape more concretely (e.g. list of sport entries), which keeps it just under a 5.

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 applies. No parameter-level confusion is possible here.

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 the public US-DK sport catalog with exact sport codes and enabled/public-contests flags. The closing sentence explicitly bounds the scope (no contests, lineups, prizes, or account data), which separates it from the many draftkings_dfs_* and draftkings_* siblings.

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 negative scoping ('does not access contests, lineups, prizes, or account data') tells the agent what this tool is not for, implicitly routing contest/lineup work elsewhere. However, it never names an alternative sibling or states a positive 'use this when you need sport codes before querying X' trigger, so the guidance is clear but not fully explicit.

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