Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

abcau_author

Retrieve an ABC News Australia author profile from a canonical URL, returning name, biography, headshot, and recent articles for byline research.

Instructions

Get an ABC News Australia author profile. Returns an ABC News Australia author profile from url, a canonical https://www.abc.net.au/news/<slug>/<id> address: name, biography, image_url and recent articles. Not every author has a headshot or biography, and wire or staff bylines often have neither.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical ABC News Australia author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose a real behavioral trait: fields are nullable (“not every author has a headshot or biography, and wire or staff bylines often have neither”). It implies a safe read via “Get,” though it says nothing about auth or rate limits.

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 tight sentences, purpose front-loaded, with the return fields and the nullability caveat following efficiently. No filler.

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?

For a single-parameter read tool with no output schema, the description covers purpose, concrete return fields, URL format, and nullability caveats. It could be marginally more complete by noting how the URL is sourced, but nothing essential 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?

Schema coverage is 100%, so the baseline is 3, but the description adds concrete meaning by spelling out the URL format (https://www.abc.net.au/news/<slug>/<id>), which the terse schema description does not.

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 (“Get”) and resource (ABC News Australia author profile), and distinguishes itself from the abcau_article/headlines/news/sections siblings. It even enumerates the returned fields, so an agent knows exactly what it retrieves.

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 – you fetch an author profile from a URL. It gives the canonical URL shape but never states when to choose this over a sibling (e.g., abcau_article) or how to obtain an author URL in the first place, and offers no exclusions.

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