Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cbssports_sections

Lists all 21 CBS Sports sections accepted by cbssports-headlines, with each section's slug, display name and feed URL for headline retrieval.

Instructions

Get CBS Sports sections. Lists the 21 CBS Sports per-sport sections accepted by cbssports-headlines, from nfl, nba and soccer to betting, prediction and general. Each has a slug, a display name and the feed url. A feed can include a story from a neighbouring sport, and off-season ones such as olympics can be weeks or months old.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose non-obvious traits: each entry has a slug/name/url, a feed may surface a story from a neighbouring sport, and inactive sections such as `olympics` can be weeks or months stale. It does not mention permissions, rate limits, or response wrapper/pagination, but for a zero-param read-only enumeration this is solid disclosure.

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 short sentences, front-loaded with the purpose, then the enumeration description, then the two freshness caveats. Every sentence adds information the agent needs (sibling linkage, record fields, stale-feed caveat) with no filler.

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?

There is no output schema, but the description compensates by describing the returned fields (slug, name, url) and the data-quality caveats around neighbouring-sport and off-season feeds. For a parameterless read-only enumeration tool, nothing an agent needs in order to call it and interpret the result is missing.

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 instead uses the space to describe the shape of each returned record (slug, name, url), which is a useful substitute for absent parameter semantics.

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+resource ('Get CBS Sports sections') and immediately scopes it as the enumeration of the 21 per-sport sections consumed by `cbssports-headlines`. That reference explicitly distinguishes it from the sibling cbssports_headlines / cbssports_news / cbssports_article tools without the agent needing to open any 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?

It clearly signals the context of use by naming `cbssports-headlines` as the consumer of these sections, so an agent can infer it should be called to discover valid section slugs before fetching headlines. It stops short of an explicit 'call this first / do not use for articles' instruction or naming a direct alternative, so it is clear context but not full when/when-not guidance.

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