Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nyt_sections

List New York Times section slugs accepted by nyt-headlines, with display names and URLs. Use to select valid sections.

Instructions

List New York Times sections. Lists the New York Times section slugs accepted by nyt-headlines, such as World and Business, each with its display name and url. It covers only the sections that endpoint takes; use nyt-categories for the broader site navigation, including Politics, DealBook and Wirecutter.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the return shape (each section's display `name` and `url`) and a real scope constraint (it covers only the sections that endpoint takes, not the full site taxonomy). It does not mention auth requirements, rate limits, or ordering, which keeps 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and alternative in three tight sentences, all of which earn their place. The first two sentences overlap slightly ('List New York Times sections' vs 'Lists the New York Times section slugs'), a minor redundancy.

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?

For a zero-parameter, read-only listing tool with no output schema, the description supplies everything needed: what is returned, the field names, the exact scope boundary, and the sibling to use for the excluded content. No meaningful gap remains.

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; there is no parameter semantics to add or omit. The description's only 'input-like' detail is which consumer endpoint the returned slugs are valid for, which is useful but not a parameter.

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 ('List New York Times sections') and immediately narrows the scope to the section slugs accepted by `nyt-headlines`. It names the sibling it is not (`nyt-categories`) and characterizes each output, so an agent can distinguish it from adjacent tools without opening a schema.

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

Usage Guidelines5/5

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

Explicitly tells the agent when to use this tool (sections accepted by `nyt-headlines`) and when to use the alternative (`nyt-categories` for broader site navigation), even naming examples the alternative covers (Politics, DealBook, Wirecutter). Nothing is left to inference.

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