Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

irishtimes_headlines

Fetch current Irish Times headlines for a chosen section such as ireland, politics, or sport to track news by topic quickly.

Instructions

Get Irish Times section headlines. Returns current Irish Times headlines for one section. section is required and takes one of 16 slugs such as ireland, politics, your-money, life-style, motors or abroad; other values return 400. Some listed articles are subscriber-only, and irishtimes-article returns a permission error for those.

Input Schema

NameRequiredDescriptionDefault
sectionYesIrish Times section slug

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, and it does disclose non-obvious behavior: invalid slugs produce a 400, and some listed articles are subscriber-only, causing permission errors in irishtimes-article. It does not describe pagination, result limits, or the shape of the returned headline list.

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 with the core action, then the required-parameter constraint, then caveats. Slightly redundant ('Get ... headlines' followed by 'Returns current ... headlines'), but every sentence carries information and nothing is padded.

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 single-param read tool with no annotations and no output schema, the description covers the essentials: the resource, the required enum param, the invalid-value behavior, and the subscriber-only gotcha. Only the return structure and any pagination behavior are left unstated.

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?

Schema coverage is 100% and the enum already lists all 16 slugs, so the baseline would be 3. The description adds genuine value beyond the schema by explaining the failure mode for out-of-enum values (400) and illustrating slug formats like `your-money` and `life-style`.

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 Irish Times section headlines') and clarifies it returns headlines for exactly one section. An agent can distinguish it from irishtimes_article, but the description never explicitly contrasts with siblings like irishtimes_news or irishtimes_sections, leaving the headlines-vs-news boundary implicit.

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?

Gives clear invocation context: `section` is required, must be one of 16 slugs, and other values return 400. It also warns which downstream lookups (irishtimes-article) will fail for subscriber-only items. It stops short of naming when to prefer this tool over irishtimes_news or irishtimes_sections.

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