Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fortune_headlines

Fetch Fortune section headlines by slug, such as finance or crypto, and return article titles and URLs for news monitoring.

Instructions

Get Fortune section headlines. Returns the latest Fortune headlines for one section. section is required and takes one of 36 slugs such as latest, fortune-500, finance, artificial-intelligence, crypto, leadership or europe. Each item has its title and URL.

Input Schema

NameRequiredDescriptionDefault
sectionYesFortune section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully states that results are latest headlines and each item contains title and URL, but it omits pagination, rate limits, and other operational context.

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?

It is front-loaded and appropriately short, with the return shape and parameter context stated efficiently. There is minor redundancy between the first two sentences.

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 simple one-parameter read tool with no output schema, the description is mostly complete: it explains the section input and the returned item fields. It could still mention pagination or sibling alternatives for fuller completeness.

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 enum fully defines the section parameter. The description adds examples and confirms 36 slugs, but does not add semantics beyond the schema's enum.

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 Fortune section headlines, with the scope limited to one section. It is clear, but it does not explicitly distinguish itself from siblings like fortune_sections or fortune_news.

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 required section parameter and examples imply how to call it for a section, but there is no explicit when-to-use guidance or comparison with alternative Fortune tools.

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