Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_year_worldwide

Retrieve the worldwide yearly box office chart for a given year, including rank, domestic and foreign grosses, shares, and title IDs.

Instructions

Box Office Mojo worldwide yearly box office. Returns the Box Office Mojo worldwide box office chart for one year. year is required and runs from 1977 to 2100. Each row is a release group with its rank, worldwide, domestic and foreign grosses, the domestic and foreign shares, and title_id; each gross also has its displayed text in a _raw field.

Input Schema

NameRequiredDescriptionDefault
yearYesBox office year, from 1977 through 2100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. Addedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that each row is a release group with rank/grosses/shares/title_id and _raw text fields, but says nothing about ordering, pagination, or whether all years 1977-2100 are populated. Decent return-shape context, missing operational traits.

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?

Front-loads the purpose in the first sentence, then documents the row shape compactly. The field enumeration is long but earns its place given there is no output schema.

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?

For a single-param read tool with no annotations, the description covers purpose, parameter range, and return fields adequately. It stops short of usage routing or pagination notes, but nothing essential to invoking it is missing.

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% for the single parameter; the description restates the same 1977-2100 range already in the schema, adding no new syntax or constraint detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Returns the Box Office Mojo worldwide box office chart for one year'), and 'worldwide' implicitly distinguishes it from the domestic sibling. It never names boxofficemojo_year_domestic, so sibling differentiation is left to inference.

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 when-to-use or when-not guidance. The 'one year' scope is stated but there is no routing to alternatives like boxofficemojo_year_domestic or the weekend charts, leaving the agent to guess why one would pick this over them.

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