Skip to main content
Glama

ottasia

by io.github.AIweather-Anurag

Search titles

search_titles
Read-onlyIdempotent

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query (movie or TV show name). English, romanized, or original-language all work.
limitNoMax number of results (1-20, default 8).
countryNo2-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.

TDQS

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.

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