Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

torontostar_author

Fetch a Toronto Star author's public profile: name, job title, biography, location, topic focus, avatar, and recent articles, using their profile slug or URL.

Instructions

Get a Toronto Star author profile. Returns one Toronto Star author's public profile: name, job title, biography, location and topic focus, avatar, and their recent articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical thestar.com/users/profile/<slug> URL; alternative to slug
slugNoAuthor profile slug (thestar.com/users/profile/<slug>); use this or url

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It transparently signals a read-only 'public profile' operation and lists the returned content, but it does not disclose error behavior, pagination for recent articles, or what happens when both slug and url are supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the primary action. It is slightly redundant in saying 'Toronto Star author profile' and then 'Toronto Star author's public profile,' but overall every sentence earns its place.

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?

Given no output schema, the description compensates by enumerating the return fields: name, job title, biography, location, topic focus, avatar, and recent articles. It is adequate for a simple, optional-parameter lookup tool, though it could clarify the shape of the recent-articles list.

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 applies. The description adds no semantic detail beyond the schema; it does not explain which parameter is preferred or what format is expected beyond what the schema already states.

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 opens with the specific verb-resource pair 'Get a Toronto Star author profile' and immediately enumerates the returned fields. This clearly distinguishes the tool from article, headline, news, and section tools in the sibling list.

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?

The description implies its usage context: retrieve an author profile rather than an article or section. However, it does not explicitly state when-not-to-use it or name alternatives such as torontostar_article for article-level lookups.

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