Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fortune_companies

Search Fortune's company directory by company name, country, industry, ranking year, revenue, or employee range to filter and retrieve matching company records as JSON.

Instructions

Search the Fortune company directory. Searches Fortune's company directory, 30 companies per page, with page starting at 1. Filter by search (company name), country, industry (exact title), ranking with year, and ranges min_revenue and max_revenue (in $M) and min_employees and max_employees. Each item has name, slug, URL, country, revenues and description. Invalid country or industry values return 400.

Input 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

A3.8/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 well: it discloses pagination (30 per page, page starts at 1), error behavior (invalid country/industry return 400), the fields in each item, and that revenues are in $M. It omits sorting, auth, and rate-limit behavior, 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.

Conciseness5/5

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

Front-loaded with purpose, then pagination, filters, item shape, and error semantics, each in a compact clause. No sentence is redundant and nothing is buried.

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?

No output schema and no annotations, yet the description covers pagination, item fields, filter dimensions, units, and error behavior, which is enough for correct invocation. Missing only secondary details like sort order or max page behavior.

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 coverage is 100%, so the baseline is 3. The description does add minor meaning: it ties ranking to year and specifies revenue units ($M) and that industry is an exact title, but most parameter detail is already in the schema.

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 ('Search the Fortune company directory') and enumerates the filterable dimensions, so the agent knows exactly what the tool returns. It stops short of differentiating itself from siblings like fortune_company (detail) or fortune_ranking (rankings), which the agent must infer.

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?

Usage is implied through the filter list (narrow the directory by name/country/industry/ranking/revenue/employees), and the 400-on-invalid note is a useful usage caveat. There is no explicit when-to-use/when-not or pointer to alternatives such as fortune_company_filters, which is only referenced inside the schema.

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