Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailystaruk_sections

List Daily Star (UK) sections and nested slugs for headlines, returning each section's slug, name, and feed URL to help you select valid feed paths.

Instructions

Get Daily Star (UK) sections. Lists the Daily Star (UK) sections accepted by dailystaruk-headlines, including nested slugs such as sport/football, news/weird-news and tech/gaming. Each entry has the slug, name and feed url. Feeds were checked on 2026-09-25 and return up to about 25 entries.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does add useful behavior: entry shape (`slug`, `name`, feed `url`), feed freshness ('checked on 2026-09-25'), and volume ('up to about 25 entries'). It doesn't restate that it's a read-only listing, but for a section index there is little risk to disclose.

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 sentences, front-loaded with purpose, then nested-slug examples, entry shape, and freshness. Each sentence carries information, though the nested slug examples and the dated freshness note are slightly more detail than strictly needed.

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?

No output schema and no annotations, so the description must cover the return shape, which it does (slug, name, url) along with freshness and count. It is nearly self-sufficient, missing only an explicit statement of how the slugs feed into `dailystaruk-headlines`.

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?

Zero parameters, so the baseline of 4 applies. The description correctly requires no parameter explanation and instead spends its words on the returned values.

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 Daily Star (UK) sections') and immediately clarifies the resource's role by tying it to the sibling `dailystaruk-headlines`. An agent can distinguish this from dailystaruk_article/headlines/news without opening a 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 link 'sections accepted by `dailystaruk-headlines`' makes the intended workflow clear: fetch this to discover valid section values. However it never states the when/when-not explicitly (e.g., 'call this before filtering headlines by section'), leaving the agent to infer the sequencing.

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