Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thestarmy_author

Retrieve The Star (Malaysia) author page by byline name or URL to get the display name, public email, and recent stories.

Instructions

Get a The Star (Malaysia) author page. Returns one The Star (Malaysia) byline's public author page: display name, the public byline email, and their most recent stories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical thestar.com.my/authors?q=<name> URL; alternative to name
nameNoByline name, matched case-insensitively, e.g. Ivan Loh

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It conveys a read-only, public lookup via 'Get' and 'public author page', and discloses returned fields. However, it does not discuss auth requirements, not-found behavior, or other operational details, leaving some ambiguity.

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 with no filler. The primary action is front-loaded, and the second sentence lists exactly what the agent can expect in the result.

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 low-complexity lookup with two well-documented optional parameters and no output schema, the description is complete. It explains the return payload (display name, email, recent stories), which compensates for the absent output schema.

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 coverage is 100%, and the parameter descriptions already explain that 'name' is a case-insensitive byline and 'url' is a canonical alternative. The tool description adds no parameter-level meaning beyond this, 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?

The description uses a specific verb ('Get') and resource ('The Star (Malaysia) author page'), and names the outlet and content type unambiguously. It distinguishes itself from sibling article/headlines tools for the same outlet and from author tools for other publications.

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 this is the tool for retrieving a The Star byline's author page, including what data it returns. It does not explicitly name alternatives or exclusion conditions, but the context is sufficiently clear for an agent to select it over sibling 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