Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thestarmy_article

Fetch The Star (Malaysia) article content from a canonical story URL, returning metadata, public body paragraphs, and paywall flags for metered or premium stories.

Instructions

Get The Star (Malaysia) article content. Returns public The Star (Malaysia) story metadata and body paragraphs from a canonical story URL. Metered and premium stories return only the public teaser paragraphs the server shows anonymous readers, flagged with paywalled; a story with no readable teaser returns a permission error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical The Star (Malaysia) story URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses paywall behavior (metered/premium returns only teaser paragraphs flagged with 'paywalled') and the permission error case for stories with no readable teaser. This is strong behavioral disclosure beyond the basic purpose.

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, each earning its place: the first states purpose, the second covers edge-case behavior. No filler.

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 tool with no output schema, the description covers the main return content (metadata, body paragraphs), the paywall flag, and the error case. It does not detail the structure of metadata or paragraphs, but that is likely acceptable for an article fetch tool.

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 description coverage is 100%, with the url parameter already described as 'Canonical The Star (Malaysia) story URL'. The description reinforces this by saying 'from a canonical story URL' but adds no new format or constraints. Baseline 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 ('Get') and resource ('The Star (Malaysia) article content'), and specifies the return (metadata and body paragraphs) from a canonical story URL. Clearly distinguishes from sibling tools like thestarmy_headlines or thestarmy_author by focusing on full article content.

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 description makes clear the tool is for fetching article content from a canonical URL, which gives an agent context for when to use it. However, it does not explicitly name alternatives or state when not to use it, leaving some inference to the agent. The context is clear enough for a single-purpose article fetcher.

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