Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_calendar_changes

Fetch Box Office Mojo's domestic release schedule changes grouped by change date. Use offset to page through 30 items at a time and see distributor, old and new dates.

Instructions

Box Office Mojo domestic release schedule changes. Returns Box Office Mojo's list of changes to the domestic release schedule, grouped by change date. offset pages through the list in steps of 30, from 0 to 780. Each change has the release, distributor, scale, old_date and new_date, and range shows the position in the list.

Input Schema

NameRequiredDescriptionDefault
offsetNoChanges page offset. Allowed values: 0, 30, 60, ... 780

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the return shape (grouped by change date, fields release/distributor/scale/old_date/new_date/range) and pagination bounds (0–780), but says nothing about freshness, rate limits, or permission/auth requirements.

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?

Three compact sentences, front-loaded with the purpose, then pagination, then return fields. No filler, though the return-field enumeration edges toward describing output that a future output schema would carry.

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, no-output-schema list tool, the description covers what it returns, how it pages, and the resulting record fields. The main gap is routing versus sibling calendar tools, but the core call information is complete.

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 coverage is 100% and the schema already documents the allowed offset values (0, 30, 60, ... 780). The description restates the same pagination steps without adding new semantics, so the schema does the heavy lifting — baseline 3.

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?

States a specific verb+resource ('Returns Box Office Mojo's list of changes to the domestic release schedule'), clearly distinguishing it from the plain boxofficemojo_calendar by focusing on changes grouped by change date. It does not name the sibling tools explicitly, so an agent infers differentiation from the wording rather than being told.

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?

There is no explicit when-to-use guidance or exclusion against the many sibling calendar tools (boxofficemojo_calendar, boxofficemojo_calendar_date, boxofficemojo_date_domestic). Pagination is described but the selection context is left to inference.

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