Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gmanews_sections

Lists 44 GMA News Online sections accepted by gmanews-headlines, including slug, display name, and URL, so you can request valid headlines.

Instructions

Get GMA News sections. Lists the 44 GMA News Online sections accepted by gmanews-headlines, each with a slug, display name and url. Slugs run from topstories and money to sub-sections such as sports-basketball and lifestyle-travel. Video, photo and TV-show sections are excluded. Takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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 does reasonably well: it discloses the return shape (slug, name, url), the cardinality (44), and a negative scope rule (video, photo and TV-show sections excluded). It does not state ordering or read-only/caching traits explicitly, but 'Get... Takes no parameters' plus a fixed list makes the safety profile evident.

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?

Six short, front-loaded sentences: purpose and routing first, then output shape, then coverage examples and exclusions. Every sentence supplies a distinct piece of information (count, fields, slug range, exclusion rule, parameter absence) with no filler.

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?

There is no output schema and no annotations, yet the description covers what the tool does, what it returns (with field names), how many items, what is excluded, and that it takes no input. An agent has everything needed to invoke and interpret this tool correctly.

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, which is the baseline-4 case, and the description confirms it explicitly with 'Takes no parameters.' No parameter semantics are needed, so this dimension is fully satisfied.

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/Lists GMA News sections') and immediately differentiates the tool from its sibling by noting these are the sections 'accepted by gmanews-headlines'. The count (44) and field set (slug, name, url) make the purpose unambiguous 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 description establishes clear context by tying the output to the `gmanews-headlines` tool's accepted values, so an agent can infer this is a lookup/discovery call. It stops short of an explicit when-to-use instruction (e.g., 'call this first to resolve a slug') or naming what to use instead if you need articles rather than sections.

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