Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gulfnews_sections

Lists the 19 top-level Gulf News sections available for headline retrieval, with each section's slug, display name, and URL.

Instructions

Get Gulf News sections. Lists the 19 top-level Gulf News sections accepted by gulfnews-headlines, such as latest-news, business, uae, world, sport and things-to-do. Each entry has a slug, display name and section url. Sub-sections such as business/aviation are not separate values; their stories appear under the parent.

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?

With no annotations, the description carries the burden and does well: it discloses the exact count (19), the return fields (slug, name, url), and an important behavioral caveat that sub-sections like business/aviation are not separate values and roll up under the parent. It does not mention rate limits or failure behavior, but for a static read-only list that is minor.

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, followed by examples and then the sub-section caveat. No filler.

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 and no annotations, the description compensates by naming the entry fields and the count of sections, and by clarifying the parent/sibling relationship. An agent has enough to call it and use the result, though it doesn't state the literal values exhaustively.

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 the baseline is 4. The description adds value by describing the shape of the returned entries and the slug format used by the parent tool, which is more than the empty schema conveys.

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 and resource ('Get Gulf News sections') and immediately scopes it as the 19 top-level sections accepted by gulfnews-headlines, clearly distinguishing it from the sibling headlines tool. Examples of section slugs make the resource concrete.

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?

By saying the sections are 'accepted by gulfnews-headlines', the description implies the tool is a discovery step for supplying section values to that sibling. It does not explicitly state when-not to use it or name an alternative, but the context is unambiguous.

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