Fetch normalized worldwide yearly box office rows from Box Office Mojo for a given year (1977–2100) as clean JSON.
Box Office Mojo worldwide yearly box office. Returns normalized release-group rows from Box Office Mojo's public worldwide yearly chart.
| Name | Required | Description | Default |
|---|---|---|---|
| year | Yes | Box office year, from 1977 through 2100 |
Changes observed during successful MCP inspections.
v1.6.0v1.6.0v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description mentions output as 'normalized release-group rows' but lacks details on data freshness, rate limits, or other behavioral traits beyond the implied read-only nature.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with purpose, zero waste. Every sentence is informative.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With only one parameter and no output schema, the description adequately explains the tool's purpose and return type. Missing some behavioral details, but sufficient for a simple tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a descriptive parameter comment ('Box office year, from 1977 through 2100'). The description adds no new meaning beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it returns 'normalized release-group rows from Box Office Mojo's public worldwide yearly chart', and the tool name includes 'worldwide', distinguishing it from siblings like boxofficemojo_year_domestic.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description implies use for worldwide yearly box office data but provides no explicit when-to-use or when-not-to-use guidance compared to alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.