Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chicagotribune_sections

List Chicago Tribune sections accepted by headline tools, returning each section's slug, display name, and URL for news, sports, opinion, and arts.

Instructions

Get Chicago Tribune sections. Lists the 60 Chicago Tribune sections accepted by chicagotribune-headlines, spanning news, suburban papers, opinion, sports teams and arts, such as crime-public-safety, daily-southtown, chicago-cubs and theater. Each has a slug, display name and page url. Tag pages and hubs that repeat the homepage are not included.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and largely meets it: it discloses the return fields (`slug`, display `name`, page `url`) and a meaningful exclusion rule ('tag pages and hubs that repeat the homepage are not included'). It stops short of stating auth or rate-limit behavior, but the scope and shape are well covered.

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?

Front-loaded with the purpose, then scope, examples, return shape, and an exclusion note. It is a little dense but every sentence adds information; nothing reads as filler.

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 zero-parameter listing tool with no output schema, the description is complete: it explains what is listed, what each entry contains, the scale ('60 sections'), and what is deliberately omitted. Nothing needed 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?

Zero parameters, so baseline is 4. The description still adds value by clarifying the vocabulary the returned slugs feed into (`chicagotribune-headlines`), which contextualizes what the agent does with the output.

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 and resource ('Get Chicago Tribune sections') and immediately distinguishes itself by naming the sibling consumer `chicagotribune-headlines`. The example slugs make the enumeration role unmistakable.

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?

By stating the sections are 'accepted by `chicagotribune-headlines`' it effectively tells the agent to call this first to discover valid slugs. It does not give explicit when-not guidance, but the usage context is clear.

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