Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_transactions_options

Retrieve NFL transaction seasons, months, and team slugs for Sportskeeda transaction pages. Use the returned values to select valid season, month, and team queries.

Instructions

List NFL transaction seasons, months and team slugs. Discovers the complete live NFL transaction season list, months for the selected season, and all team transaction page slugs. Use these values with sportskeeda-transactions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seasonNoSeason start year; current live choices: 2020,2021,2022,2023,2024,2025,2026; defaults to current

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool discovers a complete live list of seasons, months, and team slugs, which indicates a discovery/read operation. It does not mention permissions, rate limits, pagination, or error behavior, so several behavioral traits remain unspecified.

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

Conciseness3/5

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

The description is front-loaded and understandable, but the first two sentences largely restate the same output items (seasons, months, team slugs) without adding new information. It could be compressed into one clear sentence plus the usage pointer.

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 simple options-discovery tool with a fully documented schema and no output schema, the description covers the returned categories and the purpose of the values. It is nearly complete, though it could say more about the exact shape of the returned team slugs or season values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single season parameter is fully documented in the schema with its enum and default behavior. The description does not add any format, syntax, or constraint details beyond what the schema already provides, so the baseline of 3 is appropriate.

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: listing NFL transaction seasons, months, and team slugs. It also distinguishes itself from its sibling by saying the values are meant for sportskeeda-transactions. An agent can tell what this tool returns without opening the 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?

Explicitly directs the agent to use the returned values with sportskeeda-transactions, which is clear routing to the sibling tool. It does not state when not to use this tool or any prerequisites, but the intended usage context is clearly established.

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