A
license-
qualityA
maintenanceMCP Server for Indian Options — Real-time option chains, Greeks, 34+ strategies, OI analysis, IV smile, Max Pain. Works with Claude Desktop. Replaces Sensibull.
16
8
MIT
ottasia
Server Details
Where to watch X in Y? 30 Asian and Middle Eastern streaming markets, via Claude.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- AIweather-Anurag/ottasia-mcp-server
- GitHub Stars
- 1
- Server Listing
- OTTASIA
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.5/5.0
Tool DescriptionsA
Average 4.4/5 across 3 of 3 tools scored.
Server CoherenceA
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.
Available Tools
3 toolssearch_titlesSearch titlesARead-onlyIdempotentInspect
Search OTTASIA's catalog for movies or TV shows by name. Returns multiple candidates with year, type, brief overview, and country-aware OTTASIA link.
Use this when a user asks 'find me X' or when a query is ambiguous (e.g. 'joker', 'the office') and you need to clarify which title they meant before checking availability. Use where_to_watch instead when the user has already named a specific title and country and just wants the streaming providers.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Search query (movie or TV show name). English, romanized, or original-language all work. | |
| limit | No | Max number of results (1-20, default 8). | |
| country | No | 2-letter ISO country code for the resulting OTTASIA links (so clicking through opens that country's streaming context). 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. |
Tool Definition Quality
A4.8/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and non-destructive. Description adds context: returns multiple candidates, includes year/type/overview, and country-aware link, enhancing understanding beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two paragraphs, front-loaded with purpose, then usage guidance. Every sentence is informative with no redundancy or fluff.
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 3 parameters, no output schema, and sibling tools, the description covers purpose, usage, parameter details, and return value, making it fully informative for selecting and invoking the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and description adds valuable context: for q it supports multiple languages, for limit and country it explains defaults and purpose of the country parameter.
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?
Description clearly states it searches OTTASIA's catalog for movies or TV shows by name, returns candidates with year, type, overview, and country-aware link, and distinguishes from 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?
Explicitly specifies when to use ('find me X' or ambiguous queries) and when not to use (use where_to_watch for specific title and country), providing clear decision criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
whats_new_onWhat's new on a streaming serviceARead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max number of titles to return (1-30, default 15). | |
| country | No | 2-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. | |
| provider | Yes | Streaming service slug. Examples: netflix, prime-video, disney-plus-hotstar, jiohotstar, wavve, tving, viu, shahid, hoichoi, zee5, sun-nxt. Use lowercase + hyphens. |
Tool Definition Quality
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.
where_to_watchWhere to watchARead-onlyIdempotentInspect
Find which streaming services carry a specific movie or TV show in a specific Asian or Middle Eastern country.
Use this tool whenever a user asks 'where can I watch X in Y' for any of these 30 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 the matched title's official name + year + provider list grouped by category (subscription, free, free-with-ads, rent, buy). Includes a link to OTTASIA's full title page for users who want trailers, cast, or alternate-country lookups. Best for queries about availability on Netflix, Amazon Prime, Disney+ Hotstar, JioCinema, Hulu Japan, Wavve, TVING, Shahid, OSN+, iQiyi, Viu, Vidio, RCTI+, Hoichoi, Chorki, ZEE5, Sun NXT, Aha, Eros Now, and other regional Asian/MENA streamers.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Movie or TV show name. English, romanized, or original-language title all work (e.g. 'Squid Game', 'RRR', 'Pathaan', 'Dilwale Dulhania Le Jayenge'). | |
| country | No | 2-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. |
Tool Definition Quality
A4.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, clearly indicating safety. The description adds value by detailing the output (matched title, year, provider list grouped by category, a link) but does not explicitly reaffirm the idempotent or open-world nature. With annotations covering safety, the description provides moderate additional context.
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 concise at about 10 sentences, front-loads the purpose, and uses a list for markets and providers. It is well-structured and informative without excessive verbosity, though it could be slightly shorter.
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 only 2 parameters with full schema coverage, no output schema, and the presence of annotations, the description provides sufficient context: output structure, example providers, and a link for more details. It does not cover error cases (e.g., title not found), but overall it is complete enough for its complexity.
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?
Input schema coverage is 100%, so baseline is 3. The description adds meaningful extra information: title can be 'English, romanized, or original-language', with examples; for country, it lists the 30 codes and notes default to IN. This goes beyond the schema description, justifying a 4.
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 tool's purpose: 'Find which streaming services carry a specific movie or TV show in a specific Asian or Middle Eastern country.' It specifies the scope (30 markets) and provides examples of streaming services. It implicitly distinguishes from siblings like 'search_titles' and 'whats_new_on' by focusing on availability queries.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'Use this tool whenever a user asks "where can I watch X in Y" for any of these 30 markets' and lists the markets. It also says 'Best for queries about availability on...' which gives context. However, it does not mention when not to use it or differentiate from sibling tools, so a 4 is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityCmaintenancePolymarket prediction markets for Claude — market search, order books, price history, and a liquidity-rewards scanner. Credential-free.6MIT
- AlicenseBqualityBmaintenance38 AI data tools for Claude and any MCP-compatible agent — crypto, DeFi, equities, commodities, energy, real estate, government intelligence, security audits, and more.45MIT
LoneStarOracle MCP Serverofficial
Alicense-qualityDmaintenance38 AI data tools for Claude and any MCP-compatible agent covering crypto, DeFi, equities, commodities, energy, real estate, government intelligence, security audits, and more.MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.