Retrieve normalized Box Office Mojo domestic release rows for a single calendar date. Input a YYYY-MM-DD date to get structured release schedule data.
Box Office Mojo domestic release schedule date. Returns normalized release rows for one public Box Office Mojo domestic release-schedule date.
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | Calendar date in YYYY-MM-DD format |
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 must fully disclose behavior. It only states that it returns normalized release rows, omitting details like read-only nature, authentication requirements, or data scope. Minimal transparency.
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 key purpose. No redundant information. Efficient and to the point.
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 one parameter and no output schema, the description covers the core purpose. However, it lacks details about the output format ('normalized release rows') which would be helpful. Mostly complete.
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?
Only one parameter 'date' with schema description 'Calendar date in YYYY-MM-DD format'. Schema coverage is 100%, so the description adds no extra meaning beyond what is already in the schema. Baseline score of 3 applies.
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?
Description specifies verb 'returns', resource 'domestic release schedule date', and output 'normalized release rows'. It is clear but does not explicitly differentiate from siblings like boxofficemojo_calendar (which likely covers a range) or boxofficemojo_date_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?
No explicit guidance on when to use this tool versus siblings. The description implies it is for a single date, but does not state alternatives or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.