Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justwatch_age_certifications

Fetch JustWatch age certification technical names for a country using its two-letter code; defaults to US, returning 400 for invalid codes and 503 for empty results.

Instructions

Get JustWatch age certifications. Lists the JustWatch age certification technical names for a country, such as PG-13 for the US. country is a two-letter code and defaults to US. An invalid country returns 400, and an unexpectedly empty result returns 503.

Input Schema

NameRequiredDescriptionDefault
countryNoTwo-letter country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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 does usefully disclose the default country (US) and specific error behaviors (400 on invalid country, 503 on empty result), but omits auth requirements, rate limits, or the structure of the returned data beyond "technical names."

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 tight sentences, front-loaded with the core action and then adding example, default, and error context. No filler, though the trailing error-code sentence is somewhat tangential to selection.

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 single-parameter read-only lookup with no output schema, the definition covers purpose, the optional parameter and its default, and failure modes. Nothing critical to calling it correctly is missing.

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 single `country` parameter as a "Two-letter country code." The description mostly repeats that but adds the default value (US), a modest value-add over the schema, so baseline 3 is appropriate.

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?

The description opens with a specific verb+resource ("Get JustWatch age certifications") and clarifies the content as "age certification technical names for a country" with an example (`PG-13` for the US). It is clear and distinct from generic lookup siblings, though it does not explicitly name a sibling alternative to contrast against.

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 explains the parameter default (US) and error codes but gives no guidance on when to use this tool versus the many other justwatch_* enumeration tools (e.g., justwatch_genres, justwatch_providers). Usage is only inferable from the stated purpose, with no when-to-use or exclusion criteria.

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