Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

irishtimes_sections

List the 16 Irish Times sections with slugs, names, and URLs so you can pick valid section filters for headline requests.

Instructions

Get Irish Times sections. Lists the 16 Irish Times sections accepted by irishtimes-headlines: ireland, opinion, politics, business, your-money, world, sport, life-style, health, technology, culture, property, food, motors, history and abroad. Each entry has a slug, name and url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the burden and does disclose the return shape ('Each entry has a `slug`, `name` and `url`'). It doesn't state that the list is static or whether it requires auth, but for a trivial reference-listing read tool this is adequate disclosure.

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?

Two sentences, front-loaded with the purpose, followed by the enumerated values and the return shape. The long value list is data that earns its place rather than filler prose.

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, no-output-schema lookup tool, the description covers purpose, consumer, valid values, and return fields. Nothing an agent needs to call it correctly 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?

The tool takes zero parameters, so the baseline is 4. The enumeration of 16 section slugs describes values consumed by sibling tools rather than this tool's own inputs, but it usefully documents the valid domain the agent will need downstream.

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 Irish Times sections') and immediately ties the resource to its consumer ('sections accepted by `irishtimes-headlines`'). This lets an agent distinguish it from sister tools like irishtimes_headlines or irishtimes_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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase about sections being 'accepted by `irishtimes-headlines`' implicitly tells the agent this is a discovery tool for valid section values before calling a headlines/feed tool. There is no explicit when-not guidance or named alternative, but the intended use is clear from context.

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