Fetch normalized domestic release schedule rows from Box Office Mojo for a given year and month.
Box Office Mojo domestic release schedule. Returns normalized grouped rows from Box Office Mojo's public domestic release schedule. Provide year and month.
| Name | Required | Description | Default |
|---|---|---|---|
| year | Yes | Calendar year, from 1921 through 2100 | |
| month | Yes | Calendar month, 1 through 12 |
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 are provided, so the description carries the full burden. It states the tool 'returns' data, implying read-only behavior, but does not explicitly confirm no side effects, authorization requirements, rate limits, or output format details. The description is insufficient for a mutation-agnostic agent.
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?
The description is extremely concise with two sentences covering purpose and parameter hint. No redundant information. Every word earns its place.
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?
For a simple tool with two required parameters, the description covers the basic purpose and parameter requirements. However, it lacks details on output structure (e.g., what 'normalized grouped rows' means), potential pagination, or data limits. Given the absence of an output schema, more complete context would be beneficial.
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 clear descriptions for both parameters (month and year). The description simply repeats 'Provide year and month' adding no additional semantic context beyond what the schema already provides. Baseline score of 3 is appropriate.
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 the tool retrieves the 'Box Office Mojo domestic release schedule' and returns 'normalized grouped rows'. The verb 'returns' and resource 'domestic release schedule' are specific. However, it does not distinguish from sibling tools like boxofficemojo_calendar_changes or boxofficemojo_calendar_date, which may have overlapping purposes.
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?
The description only instructs to 'Provide year and month', but offers no context on when to use this tool versus alternatives (e.g., calendar_changes or calendar_date) or any prerequisites. There is no mention of use cases or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.