Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nymag_news

Fetch New York Magazine top stories as structured JSON, with titles, URLs, summaries, authors, publication times, and images. Use section headlines to access specific categories.

Instructions

Get New York Magazine top stories. Returns the current New York Magazine top stories, with no parameters. Each item has a title and URL, and may include summary, author, publication time and image. Use nymag-headlines to read one of its sections.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the return shape (title and URL always, plus optional summary, author, publication time, image) and confirms there are no parameters, which is genuinely useful context. It does not mention auth, rate limits, or freshness/pagination behavior, keeping it below 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?

Three short sentences, front-loaded with the purpose, that each carry information. The second sentence ('Returns the current New York Magazine top stories') partially restates the opening, which is minor redundancy keeping it from a 5.

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?

For a parameterless read tool with no output schema, the description covers what the tool returns (including per-item fields) and which sibling to use instead, which is complete enough to invoke correctly. Missing only secondary detail like ordering or result count.

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?

Zero parameters, so the baseline is 4. The description explicitly confirms 'with no parameters', which aligns with the empty schema and leaves nothing to guess.

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 New York Magazine top stories') and names the sibling nymag-headlines as the tool for a single section, so an agent can distinguish the two. It stops short of a full differentiation from nymag_article/nymag_sections, but the core purpose is unambiguous.

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?

Explicitly routes the agent to `nymag-headlines` for reading a section, which is a real alternative with a stated condition. However, it gives no guidance on when NOT to use this tool (e.g., vs nymag_article for a specific story), so a full 5 isn't warranted.

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