Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bleacherreport_sections

List supported Bleacher Report sections with slugs, names, and URLs to find valid values for headline queries.

Instructions

Get Bleacher Report sections. Lists the 30 Bleacher Report sections that bleacherreport-headlines accepts: 18 league and sport hubs such as nfl, tennis and olympics, plus 12 sub-hubs such as nba-draft and bracketology. Each has a slug, display name and landing-page url. Team pages, scores, standings and MotoGP are not included.

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 burden. It discloses the exact cardinality (30), the composition (18 + 12), the fields returned (`slug`, display `name`, landing-page `url`), and explicitly what is absent: team pages, scores, standings and MotoGP. It never states the operation is read-only, but a zero-parameter listing leaves little ambiguity.

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 tight sentences, front-loaded with the purpose, then scope/composition, then return shape, then exclusions. No filler and no repetition of the tool name.

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, so the description must describe returns, and it does (slug, name, url). Combined with the count, the hub/sub-hub breakdown, the downstream consumer, and the explicit exclusion list, an agent has everything needed to call it correctly and interpret the result.

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 no parameters, so the schema documents nothing and the 4 baseline applies. The description usefully reframes the zero-parameter shape as a fixed, complete enumeration rather than something that needs filtering input.

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?

Starts with a specific verb and resource ("Get Bleacher Report sections") and immediately quantifies scope: 30 sections broken into 18 league/sport hubs and 12 sub-hubs, with concrete examples like `nfl` and `nba-draft`. This distinguishes it clearly from sibling tools such as bleacherreport_headlines or bleacherreport_news.

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 ties itself to the consumer of its output: the 30 sections are the ones `bleacherreport-headlines` accepts, which tells an agent this is the discovery step before fetching headlines. It also rules out team pages, scores, standings and MotoGP, though it doesn't name a sibling tool to use for those excluded cases.

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