Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_calendar

Retrieve Box Office Mojo domestic movie release schedules for a specified year and month, grouped by date with titles, distributors, genres, cast, and poster URLs.

Instructions

Box Office Mojo domestic release schedule. Returns Box Office Mojo's domestic release schedule for one month, grouped by date. year (1921 to 2100) and month (1 to 12) are both required. Each release has its title, release_url, distributor, scale, genres, cast and poster image URLs when present.

Input Schema

NameRequiredDescriptionDefault
yearYesCalendar year, from 1921 through 2100
monthYesCalendar month, 1 through 12

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
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the return shape (title, release_url, distributor, scale, genres, cast, poster image URLs when present), which is real value given no output schema. It stops short of any other behavioral context such as data-source caveats, caching, or paging, so it is adequate but not rich.

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?

Two sentences, purpose front-loaded, requirements stated before the field enumeration. The trailing 'when present' qualifier is a nice touch. Only minor redundancy: it restates the year/month ranges already in the schema.

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?

With no output schema, the description must carry return-value information, and it does by enumerating the release fields. For a simple two-parameter, read-only list tool this is close to complete. Missing only sibling disambiguation and any note on result volume/paging.

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 schema already documents both parameters including their ranges. The description merely repeats the same ranges (1921 to 2100, 1 to 12) and adds no syntax, format, or edge-case meaning beyond the schema. Baseline 3 is appropriate.

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 states a specific verb and resource: 'Returns Box Office Mojo's domestic release schedule for one month, grouped by date.' That is unambiguous and distinguishes it from chart/list-oriented siblings like boxofficemojo_year_domestic. It does not, however, differentiate from the very close siblings boxofficemojo_calendar_date and boxofficemojo_calendar_changes, leaving the agent to guess which calendar variant to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the name and the fact that both year and month are required, and the grouping-by-date behavior hints at the use case. There is no explicit when-to-use vs. when-not, and no pointer to the near-identical calendar_date/calendar_changes tools, so an agent cannot confidently choose among them from the text alone.

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