Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gamesradar_news

Fetch current GamesRadar+ top stories with titles, URLs, summaries, publication times, authors, and images. Use it to monitor gaming news across all sections; no parameters required.

Instructions

Get GamesRadar+ top stories. Returns the current GamesRadar+ top stories. Each item has its title, URL, summary, publication time, author and image. Takes no parameters; use gamesradar-headlines for a single games, hardware or entertainment section.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does disclose the shape of the return (title, URL, summary, publication time, author, image) and that it takes no parameters. It omits auth/prerequisite and rate-limit context, but for a parameterless read-only feed this is reasonably transparent.

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

Conciseness3/5

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

The first two sentences restate the same fact ('top stories' twice), which is wasted space, though the whole description remains short and the alternative tool is front-loaded at the end.

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?

For a zero-parameter feed with no output schema, the description covers both the return fields and the sibling alternative, leaving no blocking gap for correct invocation. Only permission/precondition context is missing, which is minor here.

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 per the rubric the baseline is 4; the description correctly notes 'Takes no parameters,' confirming the schema is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('GamesRadar+ top stories') and distinguishes itself from the sibling section-based feed by naming gamesradar-headlines. The first two sentences are near-duplicates, which weakens the front-loading but does not create ambiguity about what the tool returns.

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?

Explicitly routes the agent: 'use gamesradar-headlines for a single games, hardware or entertainment section,' which tells the agent when to prefer the alternative. It does not state when this aggregate feed should be avoided, but the routing condition is clear enough.

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