Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

men_article

Fetch Manchester Evening News article content by URL, including title, authors, images, timestamps, paragraphs, and paywalled status.

Instructions

Get Manchester Evening News article content. Returns a Manchester Evening News article by url, a canonical HTTPS article link. The response has the title, description, section, authors, lead image, publish and update times, body paragraphs and a paywalled flag. Subscriber-only or blocked articles return an upstream error.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Manchester Evening News article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantive work: it enumerates the returned fields (title, section, authors, image, times, body paragraphs) and, importantly, warns that subscriber-only or blocked articles surface an upstream error rather than content. It omits auth/rate-limit details, so it stops short of a 5.

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 purpose in sentence one, then input constraint and response shape. The response-field sentence is long but earns its place since no output schema exists.

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 one-parameter fetch tool with no output schema, the description supplies the return shape and the failure mode, which is what an agent needs. The remaining gap is how an agent is expected to obtain a valid article URL, which is left to the sibling headline/section tools.

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 single parameter is already documented there; the description only adds that the URL must be canonical HTTPS, which is marginal value beyond the schema text.

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 Manchester Evening News article content') and pins the input to a canonical HTTPS article URL, which cleanly separates it from siblings like men_headlines, men_news and men_sections that enumerate rather than fetch.

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

Usage Guidelines3/5

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

Usage is implied by the single-URL fetch pattern and the sibling set, but the description never states when to use this versus men_headlines/men_sections for discovering URLs, and offers no prerequisites or exclusions beyond the paywall note.

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