Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cna_author

Fetch an author's profile from CNA, including name, job title, biography, contact email, and recent bylines, using a slug or canonical author URL.

Instructions

Get a CNA author profile. Returns one CNA correspondent's or contributor's public profile: name, job title, biography, contact email, and their recent bylined articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical channelnewsasia.com/author/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. aqil-haziq-mahmud

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 present, the description carries the burden of behavioral disclosure. It states that exactly one public profile is returned and lists its contents (name, job title, biography, contact email, recent bylined articles), which communicates read-only, public-profile behavior without requiring the agent to infer it.

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 first states the operation and scope, and the second lists the returned data. The most important identifying information is front-loaded.

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 simple 2-parameter lookup with a fully documented schema, the description is nearly sufficient: it names the resource and all major returned fields. It does not cover edge cases such as missing or invalid identifiers, but those are not critical for a straightforward profile fetch.

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%: both url and slug already have clear descriptions, including the URL format and an example slug. The description adds no parameter-level guidance beyond the schema, so the baseline of 3 is appropriate.

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 opening verb 'Get' and resource 'CNA author profile' name exactly what the tool does, and it is clearly distinct from sibling tools like cna_article, cna_headlines, or other publishers' author tools. The second sentence enumerates the returned fields, removing ambiguity about scope.

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 establishes a clear context: use this when you need a CNA correspondent's or contributor's public profile, including bylined articles. It does not name alternative tools or exclusion conditions, but the stated resource and publisher scope make the intended use apparent.

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