Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fortune_sections

List Fortune sections accepted by fortune-headlines, including latest, fortune-500, finance, tech, leadership and crypto. Each returns a stable slug, display name and URL for filtering headlines.

Instructions

Get Fortune sections. Lists the Fortune sections accepted by fortune-headlines, such as latest, fortune-500, finance, tech, leadership and crypto. Each entry has a stable slug, display name and the section url. Takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden, and it does this reasonably: it reveals the return shape (stable `slug`, display `name`, section `url`), states the data is stable, and explicitly notes it takes no parameters. It's a safe read-only enumeration, and nothing contradicts that, though it doesn't discuss pagination or ordering.

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 tight sentences: purpose first, illustrative examples second, return shape and no-parameter note last. Nothing is redundant and the most important information is front-loaded.

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?

With no output schema present, the description compensates by naming the fields each entry contains (`slug`, `name`, `url`), and for a zero-parameter enumeration tool that is everything an agent needs to call it and use the result. Nothing material is missing.

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 has zero parameters, so the schema-coverage baseline of 4 applies. The description reinforces this by explicitly stating 'Takes no parameters,' which removes any doubt an agent might have about required inputs.

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 Fortune sections') and immediately ties the resource to its consumer, `fortune-headlines`, which no sibling list-style tool does. The examples (`latest`, `fortune-500`, `finance`, `tech`) make the resource concrete rather than abstract, so an agent can distinguish this enumeration tool from fortune_headlines, fortune_news, and fortune_article at a glance.

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?

The phrase 'Lists the Fortune sections accepted by `fortune-headlines`' gives clear context: this is the lookup you consult to obtain valid section slugs for the headlines tool. It stops short of an explicit when-to-use/when-not statement or naming an alternative lookup path, so it is clear context without exclusions.

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