Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

inquirer_headlines

Fetch Philippine Daily Inquirer headlines for a specified section, returning each story's title, URL, summary, publication time, author, and lead image.

Instructions

Get Philippine Daily Inquirer section headlines. Returns the latest Philippine Daily Inquirer stories for one section. section is required and takes newsinfo, globalnation, business, sports, entertainment, lifestyle, technology, opinion, usa or cebudailynews. Each item has its title, URL, summary, publication time, author and lead image.

Input Schema

NameRequiredDescriptionDefault
sectionYesPhilippine Daily Inquirer section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does so reasonably by enumerating the returned fields (title, URL, summary, publication time, author, lead image). It omits only secondary concerns like pagination or freshness, which are minor for a read-only headlines feed.

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 and compact, with the resource named first and the return shape last. There is mild redundancy between 'section headlines' and 'stories for one section,' but nothing wasteful.

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?

In the absence of an output schema, the description usefully describes the item fields an agent will receive, and the single required parameter is well covered by the schema. Complete for a straightforward headlines retrieval tool.

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 description coverage is 100% and the enum is fully documented in the schema. The description restates the same allowed values without adding syntax, defaults, 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+resource ('Get Philippine Daily Inquirer section headlines') and clarifies scope ('latest stories for one section'). It is clear what the tool does, but it does not distinguish itself from sibling tools like inquirer_news or inquirer_sections.

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 implied: fetch headlines for a chosen section, with `section` noted as required. There is no explicit when-to-use/when-not guidance and no sibling alternative is named, so the agent must infer selection.

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