Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

njcom_news

Retrieve current NJ.com top stories from an RSS feed, including titles, canonical links, summaries, authors, publication times, and images for quick news monitoring.

Instructions

Get NJ.com top stories. Returns current NJ.com top stories from its anonymous Arc RSS feed, including title, canonical URL, short feed summary, author, publication time, and image where available. Category discovery and section headlines are deferred because the complete accepted feed taxonomy could not be verified; article and author routes remain unverified behind the site's DataDome challenge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.1/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 it does well: it discloses the data source (anonymous Arc RSS feed) and honestly flags unverified article/author routes and a DataDome challenge limiting deeper access. It does not cover auth needs or rate limits, but for a read-only public feed the caveats given are the meaningful ones.

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?

Two sentences, front-loaded with the core purpose and return shape, then the operational caveats. The rationale sentence about deferred taxonomy is slightly verbose but still earns its place by explaining real coverage limits.

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?

No output schema exists, yet the description enumerates the returned fields and the data origin, which is exactly what an agent needs to decide whether the payload fits its task. The remaining gap — no alternatives named for the deferred categories — is minor for a simple parameterless feed call.

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 there is nothing for the description to compensate for; the baseline of 4 applies. The description correctly avoids inventing parameter guidance that does not exist.

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 NJ.com top stories') and enumerates exactly what comes back (title, canonical URL, summary, author, publication time, image). Among a large set of news siblings, it is unambiguous which one this is and what it returns.

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 clearly scopes the tool to top stories and states that category discovery and section headlines are not available, which implicitly tells the agent when not to reach for it. However, it never names an alternative tool or the condition under which a different news source should be preferred, so routing guidance stops at exclusion.

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