Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

standard_article

Retrieve structured Evening Standard article content by URL, including title, authors, date, body paragraphs, and paywall status.

Instructions

Get Evening Standard article content. Returns one Evening Standard article by its canonical standard.co.uk article url. The response has the title, description, publish and update times, section, authors, lead image, body paragraphs and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Evening Standard article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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 well by enumerating the return payload: title, description, publish/update times, section, authors, lead image, body paragraphs, and a paywalled flag. It stops short of operational traits such as auth needs, rate limits, or whether content is truncated for paywalled articles.

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?

Three tightly written sentences, front-loaded with the purpose before the return-shape detail. Every sentence conveys distinct information with no filler.

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 one-parameter fetch tool with no output schema, the description compensates by listing the fields the response contains, including the notable paywalled flag. Nothing an agent needs to select or invoke the tool correctly is missing.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents it fully. The description's restatement of the canonical standard.co.uk URL adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 Evening Standard article content') and narrows scope to a single article retrieved by canonical URL. This clearly distinguishes it from the sibling standard_headlines, standard_news, and standard_sections tools, which return lists rather than one article.

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?

The need for a canonical standard.co.uk URL implies the tool is for fetching one known article, but the description never explicitly says when to use this versus standard_headlines or standard_news, nor names any alternative. Usage is inferable from the resource but not spelled out.

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