Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

thejournal_headlines

Read-only

Current TheJournal.ie headlines for one public section; section must come from thejournal_sections.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section": "<section>"
    },
    "name": "thejournal_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesTheJournal.ie section slug. Documented values: irish, politics, international, business, tech, science, environment, voices, investigates, factcheck, explainer, gaeilge, sport, money-diaries, quiz, climate-change, housing, cost-of-living, road-safety, courts, ukraine, gaza.

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. Changed1 schema field changed
    • addedInput schema / properties / section / description
      Added value: +"TheJournal.ie section slug. Documented values: irish, politics, international, business, tech, science, environment, voices, investigates, factcheck, explainer, gaeilge, sport, money-diaries, quiz, climate-change, housing, cost-of-living, road-safety, courts, ukraine, gaza."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety and openness profile. The description adds the constraint that the section must be sourced from another tool, which is useful context, but does not mention rate limits, freshness guarantees, or the fact that its scope is limited to a single section at a time. Baseline credit for adding one constraint beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

A single sentence, front-loaded with the action and resource, then the routing constraint. No filler, no redundancy. Exactly the right size for a one-parameter tool.

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?

The tool is simple (one required param, output schema present, annotations cover safety). The description covers purpose, scope, and the cross-tool dependency. It is nearly complete; a minor gap is the absence of any note about result freshness or pagination, but with an output schema those are less critical.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema already enumerates 22 documented section slugs. The description only re-iterates that the value must come from thejournal_sections, adding a cross-tool dependency but no new syntax or examples. Baseline 3 is appropriate when schema does the heavy lifting.

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 action (fetch current headlines) and a clear resource (TheJournal.ie public section). The scope is narrowed to 'one public section,' which distinguishes it meaningfully from thejournal_sections (which presumably lists sections) and thejournal_article (which fetches a full article). However, it does not explicitly name or contrast with sibling tools, keeping it just below a 5.

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?

The description tells the agent that 'section must come from thejournal_sections,' which is a concrete prerequisite and routing rule. It implies the user should call thejournal_sections first to obtain a valid slug. There are no explicit 'do not use this for X' exclusions, but the dependency guidance is clear.

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