Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gq_news

Fetch current GQ top stories as structured JSON, including title, URL, summary, author, image, and publish time; excludes galleries and non-story content.

Instructions

Get GQ top stories. Returns GQ's current top stories, with no parameters. Each item has its title, url, summary, author, image_url and published_at as an RFC 3339 UTC timestamp. Only /story/ articles are included; galleries and other content types are skipped.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/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 full burden, and it does meaningful work: it discloses the exact result shape (title, url, summary, author, image_url, published_at), the timestamp format (RFC 3339 UTC), and a non-obvious content filter (only /story/ articles; galleries skipped). It stops short of stating auth/rate-limit or freshness behavior.

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, front-loaded with the core action and then the return-shape and filtering details. No padding or restatement of the tool name.

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?

With no output schema, the description compensates by enumerating returned fields and the filtering rule, which is enough to call and interpret the tool. The only remaining gap is the unaddressed relationship to gq_headlines and similar siblings.

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?

There are zero parameters, so per the rubric baseline is 4. The description correctly notes there are no parameters, matching the empty schema, and adds nothing misleading.

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 and resource ('Get GQ top stories') and clarifies scope as current/top stories. However, it never distinguishes itself from the closely related sibling gq_headlines, so an agent cannot tell from the description alone which of the two to call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description indicates the tool takes no parameters but gives no when-to-use guidance, prerequisites, or alternatives. With siblings like gq_headlines, gq_sections and gq_author present, the absence of any routing guidance is a real gap.

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