Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

phillyinquirer_headlines

Retrieve recent Philadelphia Inquirer section headlines, excluding Associated Press wire copy, with title, URL, and optional summary, author, time, or image.

Instructions

Get Philadelphia Inquirer section headlines. Returns recent Philadelphia Inquirer stories for one section, without Associated Press wire copy. section is required and takes one of 24 slugs, such as news, sixers, eagles, south-jersey or real-estate; invalid values return 400. Each item has a title and URL, and may include summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesPhiladelphia Inquirer section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/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 behavioral burden and does well: it discloses the AP-wire exclusion, that invalid section values return a 400, and the shape of each returned item. It omits pagination, rate limits, and auth, keeping it short of a 5.

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, front-loaded with the core purpose, then constraints, then return shape. Every sentence carries distinct information with no redundancy.

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 single-parameter tool with no output schema, the description fully covers the required input, its error behavior, and what each returned item contains. 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?

Schema coverage is 100% with an enum, so the schema already documents the parameter. The description adds value beyond it by giving example slugs and specifying the invalid-value failure mode (400), which the schema does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get Philadelphia Inquirer section headlines') scoped to a single section, which clearly separates it from author/article-level siblings. It does not explicitly name which sibling to use instead, but the purpose is unambiguous.

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 'for one section' scoping and the 'without Associated Press wire copy' note imply when to use it, but there is no explicit guidance contrasting it with phillyinquirer_news or phillyinquirer_sections. Usage is implied rather than stated.

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