Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

torontostar_author

Read-only

Fetch one Toronto Star author's public profile, topic focus, and recent article links from a canonical author URL. Use torontostar_article for one story's content or torontostar_headlines for the latest outlet stories.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "torontostar_author"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / slug / description
      Added value: +"Author profile slug (thestar.com/users/profile/<slug>); use this or url"
    • addedInput schema / properties / url / description
      Added value: +"Canonical thestar.com/users/profile/<slug> URL; alternative to slug"
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and network profile is covered. The description reinforces read-only public data and lists the returned components, but with an output schema present that content is largely redundant, so it adds modest value beyond structured fields.

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 with zero waste: the capability is front-loaded and the routing hint follows immediately. Nothing could be removed without losing signal.

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?

With an output schema covering the return payload and annotations covering the safety profile, the description only needs to state scope and routing, which it does. Minor gap: it never clarifies whether url or slug is preferred when both are supplied.

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 are documented as 'use this or url' alternatives, and the description only echoes 'canonical author URL'. Baseline 3 is correct because the schema already carries the parameter semantics and the description adds no format or precedence detail.

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 (Fetch) and resource (one Toronto Star author's public profile) and enumerates the payload (profile, topic focus, recent article links). It names the two sibling tools it is not, so an agent can distinguish it without opening any schema.

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?

Explicitly routes the agent: 'Use torontostar_article for one story's content or torontostar_headlines for the latest outlet stories.' The condition selecting this tool is implied (author-level browsing) rather than stated, so it falls just short of a full when/when-not statement.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources