Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

punch_news

Fetch top Punch stories from punchng.com with title, article URL, summary, author, and corrected publication time; no parameters needed.

Instructions

Get Punch top stories. Returns the latest Punch stories from punchng.com: title, article URL, summary, author and publication time. Takes no parameters. Punch labels its times as UTC but publishes them in West Africa Time (UTC+1), and published_at is corrected for that one-hour skew.

Input Schema

NameRequiredDescriptionDefault

No arguments

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, the description carries the full burden and does reasonably well: it enumerates the returned fields, states the tool takes no parameters, and importantly discloses the UTC-vs-West-Africa-Time labeling quirk and that `published_at` is corrected for the one-hour skew. That timezone caveat is genuine behavioral context an agent could not infer. It omits pagination/result-count and rate-limit behavior, keeping it short of a 5.

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 purpose, then the return shape, then the timezone caveat. Every sentence adds information and none is 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 listing the returned fields and the timezone correction, which is sufficient for a no-param read tool. It stops short of full completeness only on pagination/ordering, which matters for a 'top stories' list.

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 explicitly confirms 'Takes no parameters', matching the empty schema with no ambiguity.

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 Punch top stories') and names the source domain (punchng.com), so the agent knows it's a news-listing tool. However, it does not distinguish itself from the very close siblings punch_headlines, punch_news, punch_article, and punch_sections, leaving the agent to guess which Punch listing to call.

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

Usage Guidelines2/5

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

The description says only what the tool does, never when to use it versus punch_headlines or the other Punch endpoints. There is no guidance on context, ordering, or exclusions, so an agent has no routing signal.

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