Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

thestarmy_article

Read-only

Fetch public The Star (Malaysia) story metadata and body paragraphs from a canonical url. Metered or premium stories return only the public teaser with paywalled set to true; if no teaser is available, the endpoint returns a permission error. Use thestarmy_headlines to find stories, thestarmy_news for the general feed, or thestarmy_author for a byline page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "thestarmy_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical The Star (Malaysia) story URL

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / url / description
      Added value: +"Canonical The Star (Malaysia) story URL"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations cover only readOnlyHint and openWorldHint. The description adds the crucial paywall behavior — metered/premium stories return the public teaser with the paywalled flag set true, and when no teaser exists the endpoint errors. That is real behavioral disclosure an agent cannot get from annotations or schema.

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 clauses in two sentences, each earning its place: what it fetches, what happens on paid content, and where to look instead. Front-loaded with the primary action and 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?

An output schema exists, so return values need no description here. Combined with the paywall behavior, error condition, and sibling routing, everything needed to call this correctly is present.

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?

Schema coverage is 100% and the url parameter is fully documented, so the baseline is 3. The description goes further by telling the agent the url must be canonical, which is the one subtle constraint that matters for this parameter, but it adds nothing else.

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 (fetch) and resources (metadata and body paragraphs) for a named publication, The Star (Malaysia). A reader knows precisely what comes back and for which outlet, distinguishing it from the many sibling *_article tools.

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

Usage Guidelines5/5

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

Names three sibling alternatives with the exact condition each serves: thestarmy_headlines for finding stories, thestarmy_news for the general feed, thestarmy_author for a byline page. That is explicit routing guidance with no inference required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources