Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fortune_ranking_lists

Retrieve comprehensive public fortune and ranking lists. Access global and regional variants, including Fortune 500 rankings and industry award data, delivered as clean JSON.

Instructions

List Fortune ranking lists. Returns every public ranking accepted by the other fortune/ranking endpoints -- the Fortune 500 franchise's regional/global variants (including Fortune China 500) plus Fortune's award and culture rankings.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the content set returned, which is real value, but says nothing about whether the operation is read-only, whether it needs auth, whether results are paginated, or how the returned list is keyed. For a zero-parameter list endpoint the safety profile is inferable from "List", but the disclosure is thin.

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?

Two sentences, front-loaded with the action, and the second sentence is devoted to scoping. The parenthetical "including Fortune China 500" and the dash clause are slightly sprawling but each carries distinguishing scope information.

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 parameters, no annotations, and no output schema, the description does the important work of enumerating what the returned list contains. The one gap is the shape of the items (identifiers/names) that an agent would need to chain into fortune_ranking, which is left unspecified.

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, so schema coverage is trivially complete and the baseline of 4 applies. The description adds no parameter detail because there is none to add.

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?

The description states a specific verb+resource ("List Fortune ranking lists") and clarifies the scope of the enumeration — regional/global Fortune 500 variants plus award and culture rankings. It implicitly distinguishes itself from the retrieval endpoints (fortune_ranking, fortune_ranking_years) but never names them, so an agent must infer the boundary.

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 phrase "accepted by the other fortune/ranking endpoints" hints that this is a discovery/enumeration step feeding the ranking endpoints, but it never states when to call this versus fortune_ranking or fortune_ranking_filters. Usage is implied rather than prescribed.

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