Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_calendar_date

Fetch Box Office Mojo domestic release schedule data for a YYYY-MM-DD date to get titles, distributors, genres, cast, and poster URLs.

Instructions

Box Office Mojo domestic release schedule date. Returns the releases scheduled on one date in Box Office Mojo's domestic release schedule. date is required, in YYYY-MM-DD form. Each release has its title, release_url, distributor, scale, genres, cast and poster image URLs when present. A date with no scheduled releases returns a not-found error.

Input Schema

NameRequiredDescriptionDefault
dateYesCalendar date in YYYY-MM-DD format

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses the return structure (title, release_url, distributor, scale, genres, cast, posters) and explicitly states that dates with no releases return a not-found error, which is valuable transparency beyond the schema.

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?

The description is appropriately sized and mostly front-loaded, but the opening noun phrase 'Box Office Mojo domestic release schedule date' is slightly redundant with the following sentence that restates the same scope.

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 one-parameter read tool with no output schema and no annotations, the description covers required input format, returned fields, and the error case. It could be slightly more complete by explicitly noting that the operation is read-only or has no side effects.

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 description coverage is 100%, so the baseline is 3. The description repeats that `date` is required and in YYYY-MM-DD form, but adds no further semantic detail such as date range limits or timezone behavior.

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?

The description clearly states a specific verb and resource: it returns releases scheduled on one date from Box Office Mojo's domestic release schedule. It does not explicitly differentiate itself from close siblings such as boxofficemojo_calendar, boxofficemojo_calendar_changes, or boxofficemojo_date_domestic, so it stops short of a 5.

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?

The description gives no guidance on when to choose this tool over alternatives, nor any exclusions or prerequisites. It only states the required date parameter and the not-found behavior.

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