Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

forbes_billionaires

Retrieve paginated Forbes billionaires list with ranking, worth, and biography data. Filter by year and control page size and offset to get structured JSON for analysis.

Instructions

Forbes billionaires list. Returns a paginated Forbes billionaires list from the public Forbes JSON feed. The default field set includes ranking, worth, person identity, citizenship, category, industry, organization, image, and biography fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoForbes list year
limitNoPage size (1-100)
startNoZero-based offset

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 present, so the description must disclose behavioral traits. It mentions it is from a public feed and returns a list, implying a read-only operation, but does not explicitly state safety, rate limits, or any side effects. It is transparent enough but minimal.

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 concise sentences with no filler. The main purpose is front-loaded and the field list is efficiently listed. Every word earns its place.

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?

The description lists the fields returned, which is useful since there is no output schema. It covers the default field set and pagination concept, but does not mention defaults for parameters (e.g., default year) or response structure details. Still, it is fairly complete for a list retrieval 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 covers all parameters with clear descriptions (year, limit, start) at 100% coverage. The description adds minimal value beyond mentioning 'paginated', which is already implied by the schema. Baseline 3 is appropriate.

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 it returns a Forbes billionaires list with specific fields. It is clear and specific, but does not explicitly differentiate from sibling tools like forbes_person or fortune_ranking, so it is not a 5.

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?

Mentions pagination and the public feed, giving context, but does not state when to use this tool over alternatives or provide exclusions. It is implied for list retrieval, but no explicit guidance.

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