Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cna_headlines

Fetch section-based CNA news headlines for asia, business, singapore, sport, or world; returns titles, URLs, and optional summaries, authors, times, and images.

Instructions

Get CNA section headlines. Returns fresh CNA headlines for one section. section is required and is asia, business, singapore, sport or world. Each item has a title and URL, and may also carry a summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesCNA section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the return shape (title and URL always, plus optional summary, author, publication time, image), which is useful, but it says nothing about authentication, rate limits, result counts, pagination, or how 'fresh' is determined.

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?

A tight, front-loaded paragraph: purpose first, then the required parameter and its values, then the response fields. No filler sentences, though the value list is mildly redundant with the enum.

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?

For a single-parameter headlines tool with no output schema, the description covers the essential context – required section and expected item fields – so an agent can call it correctly. It falls short only on refresh semantics and result volume.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is fully documented with an enum, so the baseline is 3. The description merely restates the allowed values in prose, adding no syntax, format, or meaning beyond what the schema already provides.

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?

The description opens with a specific verb and resource: 'Get CNA section headlines' / 'Returns fresh CNA headlines for one section.' It is clear what the tool does, but it makes no attempt to distinguish itself from close siblings like cna_news, cna_sections, or cna_article, so the agent must infer the boundary.

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

Usage Guidelines3/5

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

Usage is only implied – 'for one section' plus the enumerated section values tell the agent what to pass but not when to prefer this over cna_news or cna_sections. There are no exclusions, prerequisites, or alternative-routing guidance.

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