Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

torontostar_sections

Lists all Toronto Star sections accepted by the headlines endpoint, including nested paths like news/gta and sports/hockey/pwhl, so you can target valid section slugs.

Instructions

Get Toronto Star sections. Lists the 69 Toronto Star sections accepted by the headlines endpoint, taken from thestar.com's main navigation. Each has a slug, a display name and a url. Nested sections use slash paths such as news/gta, sports/hockey/pwhl and business/technology. Takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does well: it discloses the return shape (slug, name, url), the count (69), the source (main navigation), and the nested slash-path convention with concrete examples. It does not explicitly state that the list is static/read-only, but for a parameterless list tool this is a minor omission.

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?

Four tightly packed sentences, front-loaded with the core purpose and ending with the key operational fact that no parameters are needed. Every sentence earns its place.

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?

For a parameterless list tool with no output schema, the description compensates fully by describing the returned fields, the exact count, and the nested-path format with examples. An agent has everything needed to call it and interpret the result.

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?

Zero parameters, so the baseline is 4. The description also explicitly confirms 'Takes no parameters,' which is consistent with the empty schema and leaves no ambiguity.

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?

Specific verb (Get) plus specific resource (Toronto Star sections), with scope made explicit: 'the 69 Toronto Star sections accepted by the headlines endpoint, taken from thestar.com's main navigation.' This clearly distinguishes it from siblings like torontostar_headlines and torontostar_news.

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?

States that the sections are 'accepted by the headlines endpoint,' which strongly implies the intended use (discover valid section values to pass to the headlines tool). It stops short of explicitly naming an alternative tool or stating when-not-to-use, so it falls short of a 5.

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