Skip to main content
Glama
Sign In
OTT Helper MCP Server

OTT Helper MCP Server

by shreyapiu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_content_details

Retrieve detailed information about any movie or series by providing its title, including ratings, platform availability, and genre details.

Instructions

Get detailed information about a specific content

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "get_content_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTitle of the content to get details for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Get detailed information'. It does not state whether the operation is read-only, what happens when the title is not found, whether authentication is needed, or what the returned details contain.

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 a single concise sentence with no filler or repetition. It is somewhat generic, but it is efficiently structured and immediately understandable.

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

Completeness3/5

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

For a one-parameter retrieval tool, the description is minimally adequate, but the absence of an output schema and any mention of the shape of 'detailed information' leaves a gap. An agent would not know what to expect in the response or how to handle a missing title.

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%, so the title parameter is already fully documented. The description adds no extra meaning about the parameter beyond the schema, which matches the baseline for fully covered schemas.

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 states a clear action and object: 'Get detailed information about a specific content'. The required title parameter clarifies what makes the content specific. It does not explicitly differentiate itself from sibling search_content_by_title, but the read-details intent is understandable.

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?

No guidance is provided for when to call this tool versus siblings such as search_content_by_title or get_top_rated_content. The description does not mention prerequisites, exclusions, or alternative routing, leaving the agent to infer usage from the tool name alone.

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