Skip to main content
Glama
samuel-adjin

MCP Movie Assistant

by samuel-adjin

discover-movies

Find movies by genre, rating, runtime, streaming providers, and other criteria using TMDB data.

Instructions

Discover movies based on various criteria using the TMDB API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
yearNo
sortByNopopularity.desc
genreIdsNo
watchRegionNo
minimumRatingNo
maximumRuntimeNo
minimumRuntimeNo
minimumVoteCountNo
monetizationTypeNo
originalLanguageNo
watchProviderIdsNo
Behavior2/5

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

No annotations exist. The description does not disclose behavior such as pagination limits, rate limits, authentication requirements, or whether the results are exhaustive. It merely restates the TMDB origin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, but it is under-specified rather than concise. It omits essential information, making it inadequate for its purpose.

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

Completeness1/5

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

With 12 parameters, no output schema, and no annotations, the description fails to provide sufficient context. The complexity of a movie discovery tool is not addressed.

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

Parameters1/5

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

Schema description coverage is 0%. The description does not explain any of the 12 parameters, including enums like sortBy or monetizationType. This is critical given the parameter count.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Discover movies based on various criteria', which is a generic purpose. It does not specify the type of discovery or how it differs from sibling tools like search-movies.

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 on when to use this tool versus alternatives like search-movies or get-trending-movies. There is no mention of prerequisites or excluded scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/samuel-adjin/movie-assistant-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server