Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_lifetime_grosses

Retrieve lifetime gross box office charts from Box Office Mojo, filtered by worldwide or domestic area, with pagination offset for clean normalized data.

Instructions

Box Office Mojo lifetime gross chart. Returns normalized rows from Box Office Mojo's credential-free lifetime gross chart. area values: worldwide, domestic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaNoChart area. Allowed values: worldwide, domestic
offsetNoChart page offset. Allowed values: 0, 200, 400, 600, 800

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / area / enum
      Added value: +[
+  "worldwide",
+  "domestic"
+]
  2. Addedv1.6.0
  3. Removedv1.6.0
  4. Addedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It mentions 'credential-free' and 'normalized rows', but does not disclose pagination behavior, rate limits, what the rows contain, or whether the data is read-only. The read nature is implied by 'returns' but not explicitly stated.

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?

The description is two sentences and front-loads the core purpose. It wastes no words, though it could pack more useful context in the same space. It is appropriately concise but could be more informative.

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?

For a data-returning tool with no output schema and no annotations, the description is thin. It doesn't explain what 'normalized rows' look like, how offset paginates, or what fields are returned. An agent would have to rely on the schema and guess at the output structure. Incomplete for practical use.

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 both parameters are documented in the schema. The description redundantly restates the area enum values, adding no new meaning. The offset parameter is not explained in the description, but the schema already lists allowed values. 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 clearly states the tool returns normalized rows from Box Office Mojo's lifetime gross chart, identifying the specific resource and operation. It doesn't explicitly differentiate from sibling tools like weekend or year charts, but the name and description make 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus alternatives such as boxofficemojo_weekend_domestic or boxofficemojo_year_worldwide. The description doesn't mention exclusions, prerequisites, or typical scenarios, leaving the agent to infer usage from the name alone.

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