Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cnet_sections

List all 51 CNET sections accepted by cnet-headlines—top-level, second-level, ai, deals, and tv-and-movies—with slug, name, and feed URL for accurate news feeds.

Instructions

Get CNET sections. Lists the 51 CNET topics accepted by cnet-headlines: top-level and second-level topics with a recently updated feed, plus ai, deals and tv-and-movies. Each has a slug, a display name and the feed url. Deeper sub-topics are not separate sections; internet means Home Internet and security means Home Security.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses the 51-topic scope, recently updated feed constraint, return fields (`slug`, `name`, `url`), and semantic caveats like `internet` meaning Home Internet. The 'Get/Lists' framing also makes clear this is a read-only lookup.

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 description is front-loaded and tightly structured: it defines the resource, states the count and return shape, then clarifies important edge cases. Every sentence adds useful scope or interpretation.

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?

Given a zero-parameter tool with no output schema or annotations, the description supplies exactly the missing context: what it lists, how many, what each item contains, and what is excluded. An agent has enough information 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 has zero parameters, so the baseline is 4. The description appropriately spends no space on parameter semantics because there are none to explain.

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 CNET sections,' and scopes it to the 51 topics accepted by `cnet-headlines`. It also distinguishes this lookup tool from headline/article siblings by clarifying that it returns section slugs, names, and feed URLs.

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 establishes the relationship to `cnet-headlines` by saying these are the accepted topics, which tells an agent when this reference list is relevant. However, it does not explicitly state when to choose `cnet-headlines` instead or provide other exclusion cases beyond deeper sub-topics.

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