Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_weekend_domestic_by_distributor

Fetch domestic weekend box office results by distributor for a chosen year and week; returns distributor rows, or a typed not-found error when the chart page is empty.

Instructions

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

Input 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?

No annotations are provided, so the description carries the full behavioral burden. It does add one genuinely useful trait: empty upstream weekend pages return a typed not-found error rather than an empty success, which tells the agent how to interpret failure. However, it says nothing about read-only nature, rate limits, or what the returned rows contain, so coverage is partial.

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 short sentences, front-loaded with the resource and then the return/error behavior, with no padding. The opening sentence largely restates the tool name and overlaps the second sentence, which is the only minor waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description should ideally sketch what a distributor row contains and confirm the read-only nature. It covers purpose and the not-found error contract, which is the most important gap for this narrow chart-fetch tool, but leaves the return shape unspecified.

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) carry explicit range documentation in the schema. The description adds no further parameter meaning, which is acceptable given the schema already does the work, so the baseline of 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: it 'returns distributor rows from Box Office Mojo's domestic weekend by-distributor chart.' The 'by distributor' dimension clearly distinguishes it from the plain weekend chart, but it never names the sibling it is not (e.g. boxofficemojo_weekend_domestic), leaving the agent to infer the distinction from the name 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 when-to-use or when-not-to-use guidance and no mention of alternatives such as boxofficemojo_weekend_domestic or boxofficemojo_weekend_domestic_estimates. The agent can infer the usage from the name, but the description itself provides none.

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