Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

thestarmy_author

Read-only

Fetch a The Star Malaysia byline profile, public byline email, and recent story links. Use thestarmy_article for one story's content or thestarmy_news for the general feed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "thestarmy_author"
  }
}

Input Schema

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

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. Changed2 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"Byline name, matched case-insensitively, e.g. Ivan Loh"
    • addedInput schema / properties / url / description
      Added value: +"Canonical thestar.com.my/authors?q=<name> URL; alternative to name"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already carry readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context by enumerating exactly what is returned (profile, public email, recent story links), though it says nothing about pagination or count of 'recent' stories.

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, zero filler; the payload description is front-loaded and the routing guidance follows immediately. Every clause earns its place.

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 structure needn't be explained, and the description still summarizes the key payload. With annotations covering safety and 100% schema coverage on params, nothing an agent needs to call this correctly is missing.

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 only two mutually-alternative optional parameters (url, name), so the schema already fully documents them. The description adds no syntax or precedence detail beyond what the schema provides, making the baseline 3 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') plus the resource and its exact payload ('byline profile, public byline email, and recent story links'). It also names the sibling tools it is not, so an agent can distinguish it from thestarmy_article and thestarmy_news without opening any schema.

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?

Explicitly routes the agent: use thestarmy_article for one story's content, thestarmy_news for the general feed, implying this tool is for author-level metadata. The alternative-selection condition is stated rather than inferred.

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