Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

seattletimes_news

Fetch recent Seattle Times top stories across all sections, including AP wire items, with titles, canonical URLs, summaries, publication times, bylines, and lead images.

Instructions

Get Seattle Times top stories. Returns about 30 of the newest Seattle Times stories across all sections, including Associated Press wire stories. Takes no parameters. Each item has its title, canonical URL without tracking parameters, summary, publication time, author byline and lead image.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/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 a decent job: it discloses the approximate result count (~30), the recency bias, the inclusion of wire content, and the read-only nature implied by "Get." It omits operational traits such as rate limits or caching, but for a simple no-arg feed that is a minor gap.

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 sentences, front-loaded with the purpose, then scope/count, then the return fields. Every sentence adds information and none repeats the schema or title.

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?

No output schema exists, so the description correctly compensates by enumerating the returned fields (title, canonical URL, summary, publication time, byline, lead image). No annotations exist either, and behavioral coverage is adequate though not exhaustive, leaving the definition complete enough to call 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?

The tool takes zero parameters and the description explicitly confirms "Takes no parameters," matching the empty schema. Baseline 4 applies for a parameterless tool with no ambiguous inputs to explain.

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?

"Get Seattle Times top stories" states a specific verb and resource, and the follow-up sentence clarifies the scope (newest across all sections, AP wire included). However, it never distinguishes itself from the sibling seattletimes_headlines, so an agent cannot tell from the description alone which of the two to call.

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?

There is no when-to-use guidance and no mention of alternatives, despite close siblings like seattletimes_headlines, seattletimes_article, and seattletimes_sections existing. The only routing information is "Takes no parameters," which is not usage 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