Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_year_domestic

Fetch Box Office Mojo's domestic box office chart for a specific year (1977–2100), returning ranks, releases, distributors, theaters, and gross totals.

Instructions

Box Office Mojo domestic yearly box office. Returns the Box Office Mojo domestic box office chart for one year. year is required and runs from 1977 to 2100. Each row has rank, release, release_date, distributor, theaters, gross, total_gross and new_this_year, each gross also with its displayed text in a _raw field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesDomestic box office year, from 1977 through 2100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.9/5.0
Behavior4/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 discloses the return structure by listing row fields, notes that gross fields include a `_raw` display text, and specifies the year range. It does not cover auth, rate limits, or update cadence, but those are less critical for a read-only chart retrieval.

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 front-loaded and appropriately sized. The opening fragment 'Box Office Mojo domestic yearly box office.' is somewhat redundant with the following sentence, but the field list earns its space by explaining the return shape when no output schema exists.

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?

Given no output schema, the description usefully enumerates the returned row fields and clarifies `_raw` fields. It is nearly complete for a simple data-query tool, though it could say more about what the chart contains (e.g., top-N versus full list) and update frequency.

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% and the single parameter is fully documented in the schema. The description repeats the required year and its 1977–2100 range without adding format or syntax details beyond what the schema already provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 the Box Office Mojo domestic box office chart for one year.' It clearly distinguishes this tool from siblings such as boxofficemojo_weekend_domestic and boxofficemojo_year_worldwide by emphasizing domestic yearly data.

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 scope: use this for domestic yearly box office charts. However, the description does not explicitly state when to use it instead of alternatives like the weekend or worldwide tools, nor does it name any alternatives.

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