Crawlora MCP

straitstimes_article

Read-only

Fetch public Straits Times article metadata and body paragraphs from a canonical url. Subscriber-only articles return the publicly served teaser with paywalled set to true. Use straitstimes_headlines to find stories or straitstimes_news for the general feed.

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": "straitstimes_article"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Canonical The Straits Times article URL

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026
- addedInput schema / properties / url / description
```
Added value: +"Canonical The Straits Times article URL"
```
First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds genuinely non-annotation behavior: subscriber-only articles return the public teaser with `paywalled` set to true, which directly affects how an agent should interpret the result.

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 tight sentences: what it returns, the paywall caveat, then routing to siblings. The core capability is front-loaded and nothing is wasted.

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?

An output schema exists, so return values need not be described, and single-param input plus safety annotations are covered. The paywall disclosure closes the main gap; only minor matters like rate limits or auth expectations are unstated.

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 a single `url` parameter already documented as the canonical article URL, so the schema carries the semantics. The description adds no format or syntax detail beyond what the schema provides; baseline 3 is correct.

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 resource (public Straits Times article metadata and body paragraphs) scoped to a canonical `url`. It also names the sibling tools it is not, so an agent can distinguish it from straitstimes_headlines/straitstimes_news without opening schemas.

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?

Routes the agent explicitly: 'Use straitstimes_headlines to find stories or straitstimes_news for the general feed', which implies this tool is for when you already have a canonical article URL. Clear alternative guidance, though it never states an explicit 'use this when' clause or any exclusion.

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

All Crawlora MCP tools Inspect

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

Need Help?