Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

theverge_news

Fetch current top stories from The Verge with titles, URLs, summaries, authors, publication times, image URLs, and types. Use it to monitor top news without parameters.

Instructions

Get The Verge top stories. Returns the current top stories from The Verge. It takes no parameters. Each item has its title, URL and, where available, a summary, author, publication time, image URL and type. Use the headlines endpoint to read one section.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it does disclose the important behavioral facts: no parameters required and the shape of each returned item (title, URL, and conditionally summary, author, publication time, image URL, type). It doesn't mention rate limits or auth, but for a parameterless read-only feed that is a minor omission.

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

Conciseness4/5

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

Front-loaded purpose, then return shape, then the alternative-endpoint hint — all in three tight sentences with no filler. The first and second sentences overlap slightly ("top stories" stated twice), which is the only redundancy.

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?

There is no output schema, so enumerating the returned fields is exactly the compensating detail an agent needs, and it is present. Given a null-parameter read tool with no annotations, little else is required; only non-disclosed operational details like pagination or rate limits are absent.

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?

Zero parameters, so the baseline is 4. The description reinforces this with "It takes no parameters," which matches the empty schema and preempts an agent from hunting for a section or count argument.

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 opens with a specific verb+resource ("Get The Verge top stories") and defines scope as "current top stories." It also distinguishes itself from the sibling theverge_headlines by explaining that the headlines endpoint reads a single section, so an agent can route between the two without opening either 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?

It names the alternative endpoint and the condition that selects it ("Use the headlines endpoint to read one section"), which is a clear routing rule. It stops short of stating explicit when-not-to-use-this-tool conditions beyond that single comparison.

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