Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fortune_article

Retrieve complete Fortune article content and detailed metadata using its canonical URL. Access titles, authors, body paragraphs, and paywall status for structured data analysis.

Instructions

Get Fortune article content. Returns one Fortune article by its canonical url. The response has the title, description, publish and update times, section, authors, lead image, body paragraphs and a paywalled flag. Subscriber-only or blocked articles return an upstream error.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Fortune article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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 meaningful work: it enumerates the returned fields (title, times, section, authors, lead image, body paragraphs) and, importantly, discloses a `paywalled` flag plus the failure mode that subscriber-only or blocked articles return an upstream error. That error/paywall behavior is genuine behavioral disclosure an agent cannot get from structured fields. It does not mention rate limits or 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, purpose front-loaded in the first, then return shape, then failure behavior. The field enumeration is slightly list-heavy but each element is informative rather than filler. Efficient overall.

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?

With no output schema and no annotations, the description must cover return shape and behavior, and it does: it lists the response fields and explains the paywall/blocked error path. An agent has what it needs to call and interpret the result; only auth and rate-limit context are absent, which are minor for this read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single `url` param is already documented as the canonical Fortune article URL. The description's phrase 'by its canonical `url`' merely restates the schema, adding no format or normalization guidance beyond it, so the baseline 3 applies.

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 (Get) and resource (Fortune article content), and the second sentence clarifies the retrieval model: one article keyed by its canonical url. This cleanly distinguishes it from siblings like fortune_headlines, fortune_news, and fortune_sections without the agent 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 Guidelines3/5

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

The description implicitly signals usage (fetch a single article when you already have its URL), but never states when to prefer this over fortune_news or fortune_headlines, nor any prerequisites. Usage is inferable but not spelled out, which is the textbook 'implied' 3.

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