Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gamerant_sections

List all Game Rant RSS section slugs, including platform, franchise, anime, and review feeds, so you can choose valid sections for gamerant-headlines requests.

Instructions

Get Game Rant RSS sections. Lists the 178 Game Rant section slugs accepted by gamerant-headlines, covering platforms (pc-news, ps5-news, nintendo-switch-news), franchises (fortnite-news, pokemon-news, fallout-news), anime and game-reviews. Each entry has the slug, name and feed 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 are provided, so the description carries the behavioral burden, and it does so reasonably: it discloses the size of the result set (178), the categories covered, and the exact fields returned (slug, name, url). It does not explicitly restate that this is a read-only, side-effect-free lookup, but 'Get'/'Lists' plus the enumerated return fields make that clear.

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: what it returns, what the slugs are for, and the entry shape. The key routing information (accepted by gamerant-headlines) is front-loaded and every clause earns its place.

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?

For a zero-parameter listing tool with no output schema, the description supplies the return fields, the count, and representative examples, which is everything an agent needs to invoke and interpret it.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description correctly adds no fake parameter guidance.

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 ('Get'/'Lists') and resource ('Game Rant RSS sections') and immediately distinguishes itself from the sibling gamerant-headlines by noting it supplies the slugs that tool accepts. An agent can tell this is the reference/lookup tool for gamerant-headlines without opening anything.

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 situates the tool as the source of slugs 'accepted by gamerant-headlines', which effectively names the downstream alternative and the context in which to use this one. It stops short of an explicit imperative ('call this first to obtain a valid slug'), so it is strong but not fully spelled out.

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