Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

theverge_sections

Lists The Verge sections accepted by the headlines endpoint, including tech, reviews, science, and AI, with each section's slug, display name, and URL.

Instructions

Get The Verge sections. Lists the The Verge sections that the headlines endpoint accepts: tech, reviews, science, entertainment, ai, policy, gaming, mobile, apps and features. Each entry has a slug, a display name and a section url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/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 burden. 'Get' implies a read-only listing, and it discloses the enumerated contents plus the returned fields (slug, name, url), which is solid transparency. It omits auth/rate-limit context, but for a static read-only listing 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.

Conciseness4/5

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

Front-loaded purpose followed by the enum list and return shape; sentences earn their place. Minor redundancy in restating 'The Verge' twice ('Get The Verge sections. Lists the The Verge sections...').

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, the description fully covers the return values (slug, name, url) and enumerates the accepted section values, so nothing an agent needs to use it 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?

Zero parameters, so the baseline is 4. There is nothing in parameter semantics for the description to clarify, and it correctly adds no spurious parameter info.

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) and resource (The Verge sections) and immediately ties it to the sibling it serves, noting these are the values the headlines endpoint accepts. An agent can distinguish it from theverge_headlines/theverge_article without opening a 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 link to the headlines endpoint implies the use case (discover valid section values before fetching headlines), giving clear context. It stops short of an explicit 'use this when / not when' statement or naming an alternative tool directly.

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