Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cbr_sections

List all 28 CBR section slugs accepted by cbr-headlines, grouped by movies, TV, comics, anime, and games, with news, reviews, features, lists, and exclusives.

Instructions

Get CBR RSS sections. Lists the 28 CBR section slugs accepted by cbr-headlines, grouped by movies, TV, comics, anime and games with news, reviews, features and lists variants, plus lists and cbr-exclusives. Each entry has a slug (for example news-movies or comics/reviews), a display name and the feed url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description bears the disclosure burden, and it does well: it states the result is a fixed set of 28 entries with no side effects and reveals the per-entry shape (slug, name, url). It does not mention any auth or caching behavior, but for a static enumeration tool there is little else an agent needs.

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

Conciseness4/5

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

Three sentences, front-loaded with the purpose before the grouping detail and the per-entry field list. Each sentence adds information, though the enumeration of category groupings is slightly denser than strictly necessary.

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?

With no output schema and no annotations, the description carries the full load and does: it gives the count, the grouping, the accepted-slug relationship to the sibling, and the exact fields each entry contains. Nothing an agent needs to call and consume this tool 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 no parameter semantics to document and the baseline of 4 applies. The description still clarifies the format of the values produced (e.g. `news-movies`, `comics/reviews`), which is the closest analogue to parameter meaning.

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 ('Get CBR RSS sections') and immediately scopes it as the list of 28 section slugs accepted by `cbr-headlines`, which separates it from the sibling headline/article tools. An agent knows exactly what this returns without opening anything else.

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?

The tie to `cbr-headlines` ('slugs accepted by `cbr-headlines`') makes the intended workflow clear: consult this to discover valid slugs, then feed them to the headlines tool. It stops short of an explicit 'call this before cbr-headlines when you need a valid section value' instruction, so it is strong context rather than a full when/when-not statement.

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