Skip to main content
Glama

ottasia

by io.github.AIweather-Anurag

What's new on a streaming service

whats_new_on
Read-onlyIdempotent

List the latest movies and TV shows recently added to a specific streaming service in a specific country.

Use this tool when a user asks 'what's new on Netflix in India', 'any new shows on Wavve', 'what came out on Disney+ Hotstar this month', etc.

Common provider slugs to use as the provider argument: netflix, prime-video, disney-plus-hotstar, jiohotstar, hulu-japan, wavve, tving, viu, vidio, iqiyi, shahid, osn-plus, starzplay, hoichoi, chorki, zee5, sun-nxt, aha, eros-now, manorama-max, shemaroo-me, crunchyroll, apple-tv-plus, hbo-max

Country must be a 2-letter ISO code from OTTASIA's 30 supported markets (IN PK BD ID MY PH SG TH MM KH LA BN CN HK JP KR TW KZ UZ TR IL LB JO SA AE KW QA BH OM EG). Returns a list of recent arrivals with brief overviews + links. Pair with where_to_watch if the user wants details on a specific title.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax number of titles to return (1-30, default 15).
countryNo2-letter ISO country code. One of: IN, PK, BD, ID, MY, PH, SG, TH, MM, KH, LA, BN, CN, HK, JP, KR, TW, KZ, UZ, TR, IL, LB, JO, SA, AE, KW, QA, BH, OM, EG. Defaults to IN if omitted.
providerYesStreaming service slug. Examples: netflix, prime-video, disney-plus-hotstar, jiohotstar, wavve, tving, viu, shahid, hoichoi, zee5, sun-nxt. Use lowercase + hyphens.

TDQS

A4.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, idempotentHint true, and destructiveHint false. The description adds that it returns a list with brief overviews and links, but does not reveal additional behavioral traits beyond what annotations imply. With good annotation coverage, the description adds moderate value.

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 well-structured with the purpose front-loaded, followed by usage examples, parameter lists, and output notes. It is informative but could be slightly more concise without losing clarity.

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

Completeness5/5

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

Given the three parameters and no output schema, the description covers input defaults, valid values, output format (list with overviews+links), and usage context with sibling tool pairing, making it fully complete for agent invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with parameter descriptions. The description adds extra context by listing example provider slugs, explaining country codes, and noting defaults (limit default 15, country default IN), which aids the agent beyond the schema.

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 clearly states the verb 'list' and the resource 'latest movies and TV shows recently added' with specific scoping to a streaming service and country. It distinguishes from sibling tools like search_titles and where_to_watch.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage examples (e.g., 'what's new on Netflix in India'), lists common provider slugs and country codes, and advises pairing with where_to_watch for details, guiding the agent on when and how to use the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ottasia toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: search_titles for finding a title by name, whats_new_on for recent additions to a service, and where_to_watch for streaming availability. No overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: search_titles, whats_new_on, where_to_watch. No mixing of conventions.

Tool Count5/5

Three tools is well-scoped for a streaming availability server, covering the essential operations of searching, discovering new content, and checking where to watch. Not too few or too many.

Completeness5/5

The tool set covers the core tasks: title search, new arrivals discovery, and streaming availability lookup. No obvious gaps for the domain of OTTASIA's catalog and streaming information.

Resources