Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

telegraph_headlines

Fetch current The Telegraph headlines for a specified section by slug, returning each article's title and URL.

Instructions

Get The Telegraph section headlines. Returns the current headlines for one The Telegraph section. section is required and takes one of uk-news, world-news, politics, business, finance, technology, sport, culture, travel, lifestyle, health, science or opinion. Each item has its title and URL.

Input Schema

NameRequiredDescriptionDefault
sectionYesThe Telegraph section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully states that results are current headlines and that each item has a title and URL, but it does not disclose rate limits, authentication needs, pagination, or ordering behavior.

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?

The description is short and front-loaded, stating the core purpose in the first sentence. It is slightly repetitive and duplicates the enum from the schema, but it remains efficient.

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 simple one-parameter retrieval tool with no output schema, the description is largely complete: it covers the required section parameter, valid values, and the shape of returned items. Pagination and result-count details are omitted but are not essential for basic invocation.

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 coverage is 100%, and the schema already defines the section enum. The description repeats the allowed values and confirms the parameter is required, but it adds no further semantics beyond the schema.

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?

The description states a specific verb and resource: it gets current The Telegraph headlines for one section. It is clear what the tool returns, but it does not explicitly distinguish itself from siblings such as telegraph_sections or telegraph_news.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description explains that a section is required and lists valid section slugs, but it gives no guidance on when to use this tool versus alternatives. There are no exclusions, prerequisites, or sibling comparisons.

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