Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

inquirer_news

Fetch Philippine Daily Inquirer headline stories with titles, URLs, summaries, publication times, authors, and lead images. Use it to monitor Philippine national news; no parameters required.

Instructions

Get Philippine Daily Inquirer top stories. Returns the latest top stories from the Philippine Daily Inquirer's flagship national-news site, newsinfo.inquirer.net. Takes no parameters. Each item has its title, URL, summary, publication time, author and lead image.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does so reasonably well: it states the tool takes no arguments and enumerates the return fields (title, URL, summary, publication time, author, lead image), so the agent knows it is a safe read returning structured story objects. It omits item count and freshness/update cadence, which would round out the picture.

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?

Three sentences, all earning their place: purpose first, then source identity, then argument behavior and return shape. Minor redundancy in restating both the outlet name and its domain, but it is front-loaded and waste-free.

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 simple, zero-parameter news feed with no output schema, the description supplies what the agent needs: source, no-argument nature, and the shape of returned items. Only the number of stories returned and update frequency are left unspecified.

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 has zero parameters, which sets the baseline at 4. The description reinforces this with an explicit 'Takes no parameters', usefully confirming the agent cannot (and need not) pass anything.

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?

States a specific verb and resource ('Get Philippine Daily Inquirer top stories') and names the exact source domain, so the agent knows precisely what content it returns. It does not, however, differentiate itself from close siblings like inquirer_headlines or inquirer_article, leaving the top-stories vs headlines boundary to inference.

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?

The 'top stories' framing and 'takes no parameters' statement imply this is a no-argument browse/feed tool, which is adequate context for selection. But there is no explicit when-to-use guidance and no mention of alternatives such as inquirer_headlines or inquirer_article when a specific story is wanted.

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