Retrieve normalized, grouped rows of Box Office Mojo domestic release schedule changes, with offset pagination to browse recent updates.
Box Office Mojo domestic release schedule changes. Returns normalized grouped rows from Box Office Mojo's public domestic release-schedule changes page.
| Name | Required | Description | Default |
|---|---|---|---|
| offset | No | Changes page offset. Allowed values: 0, 30, 60, ... 780 |
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?
With no annotations, the description carries the full burden of behavioral disclosure. It only mentions 'returns normalized grouped rows', omitting details like pagination behavior (implied by the offset parameter), rate limits, authorization needs, or the nature of the source page. This is insufficient for safe invocation.
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, consisting of two sentences that directly state the purpose and output. No redundant information, well-structured for quick parsing.
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?
Given the lack of an output schema, the description's mention of 'normalized grouped rows' is too vague to inform the agent about the return format. The offset parameter suggests pagination but is not explained. The tool's role among many similar siblings is not clarified, leaving gaps.
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?
The schema description for the offset parameter (allowed values) is clear and covers 100% of parameters. The tool description adds no extra meaning beyond what the schema already provides, so the 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 it deals with 'domestic release schedule changes' from Box Office Mojo, which distinguishes it from other calendar tools like boxofficemojo_calendar. However, it could be more specific about what constitutes a change (e.g., delayed, added, removed releases).
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?
No guidance is provided on when to use this tool versus alternatives such as boxofficemojo_calendar or boxofficemojo_calendar_date. The agent is left to infer the context without explicit when-to or when-not-to instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.