Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_weekend_domestic_estimates

Fetch domestic weekend box office estimates and actual results for a specific year and week from Box Office Mojo.

Instructions

Box Office Mojo domestic weekend estimates. Returns estimate-vs-actual rows from Box Office Mojo's domestic weekend estimates chart. Empty upstream weekend pages return a typed not-found error rather than an empty success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
weekYesWeekend number, 1 through 53
yearYesDomestic weekend year, from 1982 through 2100

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 behavioral burden. It usefully discloses that empty upstream weekend pages return a typed not-found error rather than an empty success, which is genuine non-obvious behavior. But it says nothing about the read-only/read-only nature, any rate limits, or the shape of the returned rows beyond 'estimate-vs-actual', leaving gaps.

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 front-loaded sentences with no filler; the resource is named first and the error behavior follows. Slight redundancy in repeating 'Box Office Mojo' and 'weekend estimates' but overall efficient.

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 simple two-parameter read tool with no output schema and no annotations, the description covers what it returns and an important error edge case, which is roughly what an agent needs. The main missing piece is differentiation from the closely related sibling tools.

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%: both year (1982-2100) and week (1-53) are documented in the schema itself. The description adds no format or interpretation detail beyond what the schema already provides, so the baseline 3 applies.

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 and resource: returns estimate-vs-actual rows from Box Office Mojo's domestic weekend estimates chart. The scope (domestic, weekend) is clear. However, it does not distinguish this tool from the near-identical sibling boxofficemojo_weekend_domestic or from boxofficemojo_weekend_domestic_by_distributor, so an agent cannot tell which to pick from the description alone.

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, when-not-to-use, or alternative named. An agent gets no guidance on why it would call this versus boxofficemojo_weekend_domestic or the by_distributor variant. Usage is only implied by the scope wording.

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