Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

punch_headlines

Retrieve current headlines from a Punch topic page by section slug, returning article titles, URLs, summaries, publication times, and image URLs when available.

Instructions

Get Punch section headlines. Returns the current stories, about 30, from one Punch topic page. section is required and takes a topic slug such as news, politics, business, sports, metro-plus or top-stories; any other value is an invalid-parameter error. Each item has a title and article URL, plus summary, publication time and image URL when the page shows them.

Input Schema

NameRequiredDescriptionDefault
sectionYesPunch topic slug

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 full burden and does reasonably well: it discloses the approximate result count (~30), the fields per item, that some fields are conditional ('when the page shows them'), and the invalid-parameter failure mode. It omits read-only/auth/rate-limit context, but the returned-data behavior is well described.

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 tight sentences, front-loaded with the core purpose, then the return shape, then the parameter constraint. No filler, though the slug examples duplicate enum information that is already in the schema.

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?

There is no output schema, so the description must cover return values, and it does (title, URL, summary, publication time, image URL, ~30 items). Combined with the parameter error behavior, an agent has enough to call it correctly; auth and pagination are the only untold pieces.

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?

Schema coverage is 100% with a 36-value enum, so the baseline is already 3. The description adds real value by naming concrete slugs and stating that any value outside the valid set is an invalid-parameter error, which is behavior the enum alone doesn't convey.

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 section headlines') and scopes it to one topic page. It's clear what the tool returns, though it never explicitly distinguishes itself from siblings like punch_news or punch_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?

It tells the agent that `section` is required and that an invalid value produces an error, which usefully constrains usage. However, it offers no guidance on when to pick this over punch_news or punch_sections, so the routing decision is left implicit.

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