Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

phillyinquirer_author

Fetch a Philadelphia Inquirer author profile by slug or inquirer.com URL for name, role, biography, image, social links, and latest 20 stories. Unknown slugs return 404.

Instructions

Get a Philadelphia Inquirer author profile. Returns a Philadelphia Inquirer staff author profile by slug (for example gammage_jeff) or an inquirer.com author url; supply exactly one. The response has name, role, biography, image_url, public web social links (no email or phone) and the latest 20 stories, with no paging. An unknown slug returns a 404 error.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical inquirer.com/author/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. gammage_jeff

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, the description carries the full burden and does well: it enumerates the response fields, notes that social links exclude email/phone, discloses the fixed 20-story cap with no paging, and states that an unknown slug returns 404. It does not mention rate limits or auth requirements, but for a read-only profile endpoint the disclosed behavior is unusually complete.

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 verb+resource and then packed with only operative detail; no filler. The single long semicolon-chained sentence is dense, which slightly hurts scannability.

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?

No output schema exists, so the description must describe the return value, and it does: name, role, biography, image_url, social links, and the latest 20 stories with no paging. Combined with the 404 note and input constraints, an agent has everything needed to call and interpret it.

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%, so the baseline would be 3. The description goes beyond the schema by adding the mutual-exclusivity constraint ('supply exactly one'), a concrete slug example ('gammage_jeff'), and the canonical URL shape, which the schema only gestures at.

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 a Philadelphia Inquirer author profile') and immediately scopes what is returned. An agent can distinguish it from phillyinquirer_article/phillyinquirer_news without opening any schema.

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?

Gives clear input-selection guidance ('supply exactly one' of slug or url) and the required format for each, which is the main decision an agent faces here. It does not name a sibling alternative or state when not to use this tool, so it stops short of full routing guidance.

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