Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

punch_sections

Retrieve valid Punch topic slugs accepted by punch-headlines, such as news, politics, business, and sports, plus each name and URL.

Instructions

Get Punch sections. Lists the Punch topic slugs that punch-headlines accepts, such as news, politics, business and sports. Each entry has a slug, a display name and the topic page url. The list covers top-level topics linked from Punch's navigation or active in the 90 days before 2026-09-25.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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 well: it discloses the return shape (slug, name, url) and, importantly, the coverage scope ('top-level topics linked from Punch's navigation or active in the 90 days before 2026-09-25'), which warns the agent the list is neither exhaustive nor historical. It does not state read-only/pagination behavior, but for an enumeration endpoint the scope disclosure is the material trait.

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 sentences, front-loaded with the action, then the downstream consumer, then the entry shape and coverage window. Every sentence adds information an agent needs and none is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 supplies the entry fields (slug, name, url) and the temporal/navigational coverage constraint. Combined with the explicit linkage to `punch-headlines`, an agent has everything needed to call this and use the result.

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 schema-description baseline of 4 applies. The description correctly adds no param detail because there is nothing to parameterize, and instead documents what the entries contain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 sections. Lists the Punch topic slugs') and immediately ties the output to the sibling `punch-headlines`, which accepts those slugs. An agent can distinguish it from `punch_article`, `punch_news` and `punch_headlines` without opening any schema.

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

Usage Guidelines4/5

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

The description establishes when this tool is relevant by defining its output as the set of slugs that `punch-headlines` accepts, which effectively routes the agent to call this before a topic-filtered headlines request. It stops short of an explicit 'use this before X / do not use for Y' instruction, so it is clear context rather than full when/when-not 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