Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

phillyinquirer_sections

List the 24 Philadelphia Inquirer section slugs accepted by phillyinquirer-headlines, with each section's slug, display name, and URL for targeted headline queries.

Instructions

Get Philadelphia Inquirer sections. Lists the 24 Philadelphia Inquirer section slugs accepted by phillyinquirer-headlines, such as news, sixers, eagles and south-jersey. Each entry has a slug, display name and url. Sub-sections such as news/philadelphia are not listed because the news section already contains them.

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?

With no annotations, the description carries the full burden and does disclose useful behavior: the exact entry shape (slug, name, url) despite no output schema, and the non-obvious rule that sub-sections like news/philadelphia are deliberately excluded because news contains them. It doesn't explicitly state read-only safety, but for a fixed 0-param lookup this is minor.

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?

Three tight sentences: purpose first, then the slug examples and connection to headlines, then the edge-case exclusion. No filler; every sentence adds information an agent needs.

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 0-param lookup with no output schema, the description covers purpose, return fields, count, the sibling linkage, and the sub-section exclusion. An agent has everything required to call it and use its output correctly.

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 still adds value by enumerating the fields returned (slug, display name, url) and clarifying that slugs — not names — are the usable tokens.

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/Lists Philadelphia Inquirer sections'), gives the exact count (24) and concrete slug examples (news, sixers, eagles, south-jersey). The relationship to the sibling phillyinquirer-headlines makes the tool's distinct role unambiguous.

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?

The description ties the output directly to a sibling — these are the slugs 'accepted by phillyinquirer-headlines' — which strongly implies this is a prerequisite/discovery call before using that tool. It stops short of an explicit 'call this before X' instruction, so it's clear context without a stated when-not.

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