Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

skysports_author

Fetch a Sky Sports author profile from a canonical URL, returning name, job title, biography, and article links with summaries and publication details.

Instructions

Get a Sky Sports author profile. Returns a Sky Sports author's name, current job_title, biography paragraphs and the article links on their profile page, from an author url such as https://www.skysports.com/author/kaveh-solhekol-773. Each article has a title and URL, with summary, author, publication time and image where present.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "skysports_author"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Canonical Sky Sports author URL

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.7Oct 1, 2026

TDQS

A4.3/5.0

Behavior4/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 clearly discloses what data is returned (name, job_title, biography, article links with summary/author/time/image), which adds substantial behavioral context. It does not mention rate limits or error behavior, but those are minor for a read-only lookup.

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 purpose, followed by a precise field list and example. Every sentence earns its place and no detail is wasted.

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?

No output schema exists, so the description explains return values thoroughly. One required parameter is fully covered. For a simple read-only lookup, nothing an agent needs in order to call 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?

Schema coverage is 100%, so the baseline is 3. The description adds an example canonical URL, which clarifies the expected format beyond the schema's 'Canonical Sky Sports author URL'. That example earns a bump to 4.

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 uses a specific verb ('Get') and resource ('Sky Sports author profile') and enumerates the returned fields. It distinguishes itself from siblings like skysports_article by focusing on the author profile page. The example URL makes the target unambiguous.

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?

It implies usage when an author URL is available, but gives no explicit when-to-use guidance, no alternatives, and no exclusions. An agent must infer that this tool is for author pages versus article or headline tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server