Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

walesonline_author

Fetch a WalesOnline author's public profile and recent articles, including name, job title, bio, email, and X/Twitter handle when available.

Instructions

Get a WalesOnline author profile. Returns one WalesOnline author's public profile (name, plus job title, bio, email and X/Twitter handle when the author lists them) and one page of their recent articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical walesonline.co.uk/authors/<slug>/ URL; alternative to slug
pageNo1-based page number of the author's article list (1 to 100); overrides any pageNumber in url
slugNoAuthor slug, e.g. rahaf-ali

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden. It clearly states the read-only intent ('Get'), describes the returned profile fields, notes conditional fields ('when the author lists them'), and specifies that only one page of recent articles is returned. This gives a solid behavioral picture, though failure modes and auth needs are not discussed.

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 front-loaded sentences with no filler: the first states the action, the second lists the return contents. It avoids repeating schema details and earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is useful because there is no output schema, and it explains the profile fields and article page return. However, it does not state that at least one of slug/url is required to identify the author, and with 0 required parameters this is a potential misuse gap.

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%, so the baseline is 3. The description adds minimal parameter-specific meaning beyond the schema; it only reinforces that one page of articles is returned, which aligns with the page parameter.

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 names a specific verb and resource ('Get a WalesOnline author profile') and details the returned content: public profile fields plus one page of recent articles. This distinguishes it from walesonline_article and other outlet-specific author tools by scope and output.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to use this tool versus sibling alternatives, such as walesonline_article or other author-profile tools. There is no when-not/alternative routing; the only usage signal is the purpose statement itself.

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