Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fortune_companies

Search and filter Fortune's public company directory by name, country, industry, revenue, employees, and ranking year. Get paginated results of 30 companies per page.

Instructions

Search the Fortune company directory. Returns companies from Fortune's public company directory (9,000+ companies as of 2026-09-23) with search, filtering, and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number; 30 companies per page
yearNoRanking year the ranking filter is evaluated against; defaults to the current year
searchNoCase-insensitive company-name search
countryNoCountry/territory slug or title; call fortune-company-filters for the complete accepted set
rankingNoFortune ranking slug to filter companies that appear on it; call fortune-company-filters for the accepted set
industryNoExact industry title; call fortune-company-filters for the complete accepted set
max_revenueNoMaximum revenue in $M
min_revenueNoMinimum revenue in $M
max_employeesNoMaximum employee count
min_employeesNoMinimum employee count

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility. It states the tool returns companies and supports search/filtering/pagination, but omits important details like dependencies on fortune-company-filters for valid filter values, any rate limits, or that it is a read-only operation. The description also lacks specifics on pagination behavior.

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?

Two short sentences with the core action front-loaded. The company count and as-of date add useful context without padding. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description does not mention that several filter parameters (country, ranking, industry) require calling fortune-company-filters first, nor does it describe the return structure. With no output schema, an agent is left without guidance on what fields to expect or how to interpret the response. This is a significant gap for a 10-parameter search 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%, so the baseline is 3. The description adds only generic 'search, filtering, and pagination' without detailing any parameter-specific semantics. It does not add value beyond what the schema already provides.

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 'Search' and resource 'Fortune company directory', clearly distinguishing it from sibling tools like fortune_article and fortune_author. The mention of search, filtering, and pagination makes the scope unambiguous.

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 implies the tool is for finding companies in the Fortune directory, but it does not explicitly state when to use it over alternatives or mention any exclusions. It doesn't reference sibling tools or conditions for use, so an agent must infer the usage context.

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