Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

thejournal_news

Read-only

Fetch TheJournal.ie top stories from the public feed; returns headline items from the general top-story stream. For a section-specific list, use thejournal_headlines with a supported section slug. Use thejournal_sections to discover section slugs. Use thejournal_article with a returned article URL when you need one story's body.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "thejournal_news"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that the source is a public feed (implying no auth) and that the payload is headline items rather than full bodies, which is useful behavioral context beyond the annotations. It doesn't cover freshness, pagination, or rate limits, so it stops 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?

Four short sentences, purpose front-loaded first, then the routing alternatives in a logical order (section list, slug discovery, single article). Slightly repetitive in structure ('For a section-specific list... Use thejournal_sections... Use thejournal_article...') but every sentence carries routing value.

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 feed tool with an output schema, the description supplies everything needed: what it returns, that it is unfiltered, and which sibling to use for each adjacent need. Return-value detail is legitimately delegated to the output schema.

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 and the schema confirms additionalProperties=false, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter meaning is needed or missing.

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?

Names a specific verb (Fetch) and resource (TheJournal.ie top stories from the public feed) and states the scope limitation: general top-story stream, not section-specific. An agent can distinguish it from thejournal_headlines, thejournal_sections, and thejournal_article without opening any 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 routes the agent to alternatives with conditions: use thejournal_headlines 'for a section-specific list', thejournal_sections 'to discover section slugs', and thejournal_article 'when you need one story's body'. This is a near-complete when-to-use map for the sibling cluster.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources