Skip to main content
Glama
Sign In
OTT Helper MCP Server

OTT Helper MCP Server

by shreyapiu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_top_rated_content

Retrieve top-rated movies and series from OTT platforms. Filter by genre, content type, and result count to get tailored recommendations based on your preferences.

Instructions

Get the highest-rated OTT content

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_top_rated_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
genreNoFilter by specific genre (optional)
limitNoMaximum number of results (default: 10)
contentTypeNoFilter by content type (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility. It states the action but does not explicitly mention that it is read-only, how the 'highest-rated' metric is defined, or that it returns a list with a default limit.

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?

The description is a single, clear sentence with no unnecessary words or details, making it highly concise and well-structured.

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 query tool with three optional parameters, the description is adequate. It does not specify the output format, but that is not explicitly required given the absence of an output schema. The context of 'content' and 'highest-rated' is sufficient for most agents.

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% (all three parameters have descriptions). The descriptions are concise and accurate, such as 'Filter by specific genre' and 'Maximum number of results', so the schema itself carries the semantic weight.

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 function: 'Get the highest-rated OTT content' uses a specific verb and resource, and the qualification 'highest-rated' distinguishes it from sibling tools like search_content_by_title or get_recommendations_by_platform_and_rating.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus its siblings. It does not mention that it is appropriate for broad top-rated queries or that more specific criteria should use other tools.

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