Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

newsmax_sections

List Newsmax RSS section slugs accepted by newsmax-headlines, with name and URL for each. Use it to find valid sections such as newsfront, scitech, or finance-headlines.

Instructions

Get Newsmax RSS sections. Lists the 20 Newsmax section slugs accepted by newsmax-headlines, such as newsfront, scitech, street-talk and global-talk. Each entry has its slug, display name and url. insiders is the combined opinion section, and finance-headlines is the finance section's Headlines listing.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 and largely does so: it discloses the return is a fixed set of 20 entries with slug/name/url, and clarifies two ambiguous entries (insiders = combined opinion, finance-headlines = finance Headlines). For a read-only discovery tool this is solid, though it doesn't state stability/refresh behavior.

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?

Front-loaded with purpose, then examples, then output fields, then two clarifying notes. Every sentence adds information, though the example slug list and the two trailing notes make it slightly denser than strictly necessary.

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?

There is no output schema, so the description must explain returns and it does (slug, name, url, count of 20). Combined with the newsmax-headlines linkage, an agent has enough to call and use it, though it doesn't confirm whether the list is exhaustive or stable over time.

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 the schema has nothing to document and the baseline is 4. The description correctly mentions no input arguments and instead documents the output shape, which is the only meaningful semantic content here.

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 Newsmax RSS sections') and defines exactly what is returned: the 20 section slugs with slug, name and url. It also distinguishes itself by naming newsmax-headlines as the consumer of these slugs, so an agent can place it relative to a sibling.

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 makes the workflow clear by stating the slugs are 'accepted by newsmax-headlines', which implies you call this first to discover valid section values. It does not phrase an explicit when/when-not rule or list alternatives, so it stops short of a 5.

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