Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_weekend_domestic

Fetch domestic weekend box office rows for a given year and week from Box Office Mojo, returning clean chart data or a typed not-found error.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>",
      "week": "<week>"
    },
    "name": "boxofficemojo_weekend_domestic"
  }
}

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

No annotations are provided, so the description must carry behavioral disclosure. It usefully states that empty upstream pages return a typed not-found error rather than an empty success, but it does not describe authentication, rate limits, or return shape beyond 'rows'.

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 brief and front-loads the returned data source before the error behavior. The opening sentence largely restates the tool name, but overall it is efficient and has no wasted elaboration.

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?

For a simple two-parameter retrieval tool with full schema coverage, the description covers the basic source and one error behavior. However, with no output schema, it remains vague about what 'rows' contain and does not help distinguish the sibling weekend-domestic variants.

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 the year and week ranges. The description adds no further parameter meaning beyond what is in the input schema, which is the baseline for full schema coverage.

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 clear retrieval action and resource: returns rows from Box Office Mojo's domestic weekend chart. It does not distinguish itself from closely named siblings like boxofficemojo_weekend_domestic_by_distributor or boxofficemojo_weekend_domestic_estimates, so an agent must infer the difference.

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?

The description gives no when-to-use guidance and does not name alternatives or conditions for selecting this tool over the by-distributor or estimates variants. It only describes an error condition, not usage context.

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