Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

foxsports_headlines

Fetch current FOX Sports headlines for a chosen section slug, such as nfl, nba, or fifa-world-cup. Provide a valid sport or topic slug to get curated headlines.

Instructions

Get FOX Sports section headlines. Returns current FOX Sports headlines for one sport or topic. section is required and takes one of 23 slugs such as top, nfl, nba, college-football, ufc, golf or fifa-world-cup; others return an invalid-parameter error. Feeds follow FOX Sports' own curation and can include related cross-sport items.

Input Schema

NameRequiredDescriptionDefault
sectionYesFOX Sports section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose two non-obvious behaviors: invalid slugs return an invalid-parameter error, and feeds follow FOX Sports' own curation and may include cross-sport items. It says nothing about return format, item count, pagination, or freshness, which leaves meaningful gaps for a feed tool.

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?

Three front-loaded sentences with no filler: purpose first, then the required parameter and its failure mode, then the curation caveat. Every sentence carries information an agent needs.

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 single-parameter feed tool with no output schema, the description covers what the tool returns conceptually, the required input, and the error condition. It stops short of describing the shape or size of the returned headline list, which is the one remaining gap.

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 description coverage is 100% and the enum already lists all 23 slugs, so the baseline is 3. The description adds only the count ('23 slugs'), a few examples, and the invalid-parameter consequence, which is marginal value over the enum itself.

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?

States a specific verb and resource: 'Get FOX Sports section headlines' and 'Returns current FOX Sports headlines for one sport or topic.' The purpose is unmistakable, but it never names or differentiates itself from the close siblings foxsports_news and foxsports_sections, so the agent must infer the distinction.

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?

Usage is implied by 'for one sport or topic' and the required `section` slug, but there is no explicit when-to-use guidance, no prerequisites, and no named alternative (e.g. foxsports_news for non-headline coverage). The agent is left to infer when this beats a sibling.

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