Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

phillyinquirer_news

Retrieve current Philadelphia Inquirer news stories in JSON without parameters, including titles, URLs, summaries, publication times, and authors; AP wire copy is excluded.

Instructions

Get Philadelphia Inquirer top stories. Returns the current Philadelphia Inquirer top stories, with no parameters. Each item has a title, canonical URL, summary, publication time and author name when available. Associated Press wire copy, which makes up much of the source, is excluded.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It usefully discloses that Associated Press wire copy is excluded and enumerates the returned fields (title, URL, summary, time, author), which is genuine behavioral context. However, it says nothing about freshness/refresh cadence, result limits, or ordering beyond 'top stories'.

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 core action and kept to three short sentences. The first two sentences are somewhat redundant ('Get top stories' / 'Returns the current top stories'), a minor waste of space.

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?

For a parameterless feed with no output schema and no annotations, the description covers the essentials: what is returned, the shape of each item, and a notable inclusion exclusion. The main gap is not distinguishing this from the near-identical headlines sibling.

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?

The tool takes zero parameters, so the baseline is 4. The description explicitly reinforces 'with no parameters', removing any ambiguity for the agent.

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 top stories', then confirms it's the 'current' feed. It is clear what the tool returns, but it does not differentiate itself from the sibling phillyinquirer_headlines, which an agent would reasonably confuse with this.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance. With siblings like phillyinquirer_headlines, phillyinquirer_sections and phillyinquirer_article available, the description should say why an agent would pick this over those, but it offers nothing.

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