Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thejournal_news

Fetch TheJournal.ie top stories across all sections. Get titles, canonical URLs, summaries, RFC 3339 publication times, and lead images for current news monitoring.

Instructions

Get TheJournal.ie top stories. Returns the latest TheJournal.ie stories across all sections. Each item has a title, canonical URL, short summary, publication time (RFC 3339, UTC) and lead image. Items carry no author byline; the article endpoint supplies it. It takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

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 behavioral burden well: it describes returned fields (title, canonical URL, summary, publication time in RFC 3339 UTC, lead image) and a key limitation (no author byline; use the article endpoint for that). It does not cover pagination or auth behavior, but those may be irrelevant for a no-parameter top-stories endpoint.

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 and efficient, with no major filler. The first two sentences slightly overlap in stating that it gets/returns top stories, but the overall structure is tight and the return-field enumeration is useful.

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 tool with no output schema, the description is complete: it explains the scope, enumerates the returned fields, flags the absence of author bylines, and points to the sibling endpoint that provides them. No critical information for correct invocation is missing.

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?

Parameter count is 0, so the baseline is 4. The description also explicitly states 'It takes no parameters,' which is exactly the parameter semantics an agent needs.

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 TheJournal.ie top stories' and 'Returns the latest TheJournal.ie stories across all sections.' It also distinguishes from the article endpoint by noting author bylines are absent here, though it does not explicitly differentiate from sibling tools like thejournal_headlines or thejournal_sections.

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?

Provides clear context for use: no parameters, top stories across all sections. It also names an alternative endpoint for author byline data, but stops short of explicitly saying when to use this tool versus thejournal_headlines, thejournal_sections, or other news siblings.

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