Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

smh_author

Fetch a Sydney Morning Herald journalist's profile and recent stories from a canonical SMH URL. Returns bio, headshot, contact email, and social links.

Instructions

Get a Sydney Morning Herald journalist profile. Returns a Sydney Morning Herald journalist's public profile -- name, short biography, headshot, contact email and social links where published -- plus their recent stories, from a canonical https://www.smh.com.au/by/- URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical The Sydney Morning Herald journalist URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the profile composition and 'where published' nuance, but doesn't mention failure modes, story pagination, or whether the operation is read-only, leaving some behavioral gaps.

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, front-loaded with the action and resource, with every clause earning its place: return fields and the URL pattern are both essential. 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?

For a simple one-parameter tool with no output schema and no annotations, the description is complete: it specifies the required input format, states what the tool returns, and notes that links are included only where published. Nothing needed to invoke it correctly is missing.

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?

The schema already describes 'url' at 100% coverage, but the description adds the concrete URL pattern (https://www.smh.com.au/by/<name>-<id>), which gives the agent actionable format information beyond the schema's generic phrasing.

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 and resource ('Get a Sydney Morning Herald journalist profile') and enumerates the returned fields: name, biography, headshot, contact email, social links, recent stories. It clearly differentiates from sibling author tools for other outlets and SMH article/headline tools.

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?

Provides clear context: use when you need an SMH journalist's profile from its canonical /by/<name>-<id> URL. It doesn't name alternatives or explicit exclusions, but the resource scope and URL constraint make the intended use unambiguous.

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