Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

straitstimes_author

Retrieve a The Straits Times author profile from a canonical author URL, including name, email, and recent articles with metadata.

Instructions

Get a The Straits Times author profile. Returns a The Straits Times author's profile by url, a canonical straitstimes.com/authors/<slug> link: name, email when the author's page publishes one, and recent articles with title, URL, summary, author, image, type and publication time.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical The Straits Times author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose what the call returns: name, conditional email, and recent articles with their fields. It reads as a read-only profile fetch, though auth/permission and rate-limit behavior are not addressed.

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?

Two sentences, front-loaded with the action and followed by return contents. There is mild redundancy between 'Get a ... profile' and 'Returns a ... profile' and a small article artifact ('a The Straits Times').

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?

No output schema exists, so describing return values is essential and is handled thoroughly. For a one-parameter retrieval tool this is near complete, with only usage context against siblings left implicit.

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% so the schema already documents `url`; the description nonetheless adds format guidance by specifying the canonical `straitstimes.com/authors/<slug>` shape, which is meaningful beyond the schema's generic label.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb 'Get' plus specific resource ('The Straits Times author profile') scoped by a canonical URL, and the return contents are enumerated. It does not explicitly distinguish itself from siblings like straitstimes_article or straitstimes_headlines, but the resource is unambiguous.

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 only implied: it takes a canonical authors/<slug> URL, so an agent can infer it is a lookup requiring that URL. There is no statement of when to prefer it over straitstimes_article, straitstimes_news, or sister author tools.

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