Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nydailynews_sections

List New York Daily News section slugs, names, and URLs to supply valid section inputs for headline queries, excluding topic and off-site pages.

Instructions

Get New York Daily News sections. Lists the 36 New York Daily News section slugs accepted by nydailynews-headlines, such as crime-public-safety, new-york-mets, nfl and things-to-do. Each entry has its slug (the last path segment of the section URL), display name and url. Topic (/tag/...) pages and off-site properties are not sections.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden, and it does disclose the return shape (each entry has `slug`, `name`, `url`), the exact cardinality (36), and the slug format ('last path segment of the section URL'). For a zero-parameter read-only enumeration there is little further behavior to reveal, though nothing is said about static vs. live data.

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 that are front-loaded with the core purpose, followed by the consumer tool and the field structure. The opening 'Get New York Daily News sections' borders on restating the name, but the remainder is dense 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?

With no output schema, the description compensates by enumerating the returned fields and count, and by ruling out non-section pages. It is essentially complete for a static, zero-param lookup, with only minor omissions like caching/refresh behavior.

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 input schema has zero parameters, so the baseline is 4. The description correctly describes only the output records rather than implying inputs, and defines the meaning of `slug` (last path segment of the section URL), which adds value even though it applies to the response.

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 New York Daily News sections') and immediately disambiguates from siblings by naming the consumer tool, `nydailynews-headlines`, and contrasting with `nydailynews-news`/article tools. It even quantifies the result set (36 slugs) and gives concrete examples, so an agent knows exactly what this returns.

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?

It clearly frames the tool as a lookup that feeds `nydailynews-headlines`, which implies when to call it (before filtering headlines by section). It also adds an exclusion ('Topic (/tag/...) pages and off-site properties are not sections'), but does not spell out an explicit when-not-to-use or list alternative category tools.

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