Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

foxsports_sections

Lists FOX Sports news sections with slugs, names, and URLs, enabling selection of feeds like top, MLB, NFL, and soccer for headline queries.

Instructions

Get FOX Sports news sections. Lists the 23 FOX Sports editorial feeds accepted by foxsports-headlines, including top, mlb, nfl, soccer, olympics and wwe. Each entry has the slug, name and feed url. The All Headlines feed is served by foxsports-news, not as a section; checked 2026-09-28.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "foxsports_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.7/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 of disclosure. It states the number of sections, gives examples, describes the returned fields (`slug`, `name`, `url`), and clarifies that All Headlines is not included. It does not mention permissions or rate limits, but for a static, parameterless editorial list this is largely sufficient.

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?

The purpose is front-loaded in the first sentence. Each following sentence adds distinct value: the feed count and examples, the returned fields, and the All Headlines exclusion with a checked date. There is no redundant or filler language.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complexity is low: zero parameters and no output schema. The description compensates by explaining what the tool returns (`slug`, `name`, `url`) and by resolving the main ambiguity around All Headlines. An agent has enough information to call it and use its output correctly.

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 has zero input parameters, so the baseline is 4. The description does not need to explain parameter semantics, and it correctly focuses on what the tool returns instead.

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?

The description uses a specific verb and resource: 'Get FOX Sports news sections.' It states the exact count (23 feeds), gives examples, and distinguishes this tool from both `foxsports-headlines` (which accepts these slugs) and `foxsports-news` (which serves All Headlines). An agent can identify this as a section-discovery tool 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says the feeds are 'accepted by `foxsports-headlines`', implying this tool should be used to discover valid slugs before calling the headlines tool. It also explicitly excludes All Headlines by routing that case to `foxsports-news`, so the when-to-use and when-not-to-use conditions are clear.

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