Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gamesradar_sections

List GamesRadar+ sections accepted by gamesradar-headlines, with slug, name, and URL for top-level hubs and sub-sections to target headline retrieval.

Instructions

Get GamesRadar+ sections. Lists the 21 GamesRadar+ sections accepted by gamesradar-headlines, from top-level hubs like games, hardware and entertainment to sub-sections such as games-guides, hardware-reviews and entertainment-streaming. Each entry has the slug, name and url.

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, so the description carries the full burden. It discloses the fixed size (21 sections) and the exact return shape (slug, name, url), which is meaningful behavioral context for a read-only enumeration tool. It does not mention caching/permissions, but for a trivial public read that is a minor gap.

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 sentences, front-loaded with the purpose, then the routing context, then the return format. Every sentence adds distinct information with no redundancy.

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 params, the description must carry the return semantics itself, and it does by naming the fields (slug, name, url) and the count. 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 baseline is 4. The description appropriately spends no space on inputs and instead documents the entries returned.

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 GamesRadar+ sections') and immediately differentiates scopally by tying the result to what `gamesradar-headlines` accepts. The examples (top-level hubs vs sub-sections) make the resource concrete, so an agent can distinguish it from gamesradar_article/headlines/news without opening 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?

The description tells the agent the purpose context: these are the sections 'accepted by `gamesradar-headlines`,' which implicitly routes the agent to call this before filtering headlines by section. It stops short of an explicit when/when-not or naming an alternative tool, but the linkage is a clear usage signal.

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