Skip to main content
Glama
AmeliaMiddleton

moviefinder-mcp

get_similar

Retrieve movies similar to a specified title by matching keywords and genres.

Instructions

Get movies similar to the given movie (matched on keywords/genres).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
movie_idYesTMDB movie ID to find similar titles for.

Implementation Reference

  • The actual handler function for the 'get_similar' tool. Calls TMDB /movie/{id}/similar endpoint and returns summarized results.
    export async function getSimilar(args: { movie_id: number }) {
      const data = await tmdbGet<PaginatedResponse<MovieListItem>>(
        `/movie/${args.movie_id}/similar`,
        { language: "en-US" },
      );
      return {
        total_results: data.total_results,
        results: data.results.map(summarizeMovie),
      };
    }
  • Schema definition for the 'get_similar' tool. Defines 'movie_id' as a positive integer describing the TMDB movie ID.
    export const getSimilarSchema = {
      movie_id: z.number().int().positive().describe("TMDB movie ID to find similar titles for."),
    };
  • src/index.ts:88-93 (registration)
    Registration of the 'get_similar' tool with the MCP server, including its description, schema, and wrapped handler.
    server.tool(
      "get_similar",
      "Get movies similar to the given movie (matched on keywords/genres).",
      getSimilarSchema,
      wrap(getSimilar),
    );
Behavior2/5

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

No annotations provided, so description must replace them. It only mentions matching on keywords/genres, lacking details on side effects, limits, or authentication requirements. The tool appears read-only but is not stated.

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?

A single sentence that is concise and front-loaded, containing only essential information without any wasted words.

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?

Given no output schema, the description could mention return format or pagination. For a simple tool, it meets minimal requirements but lacks completeness in expected behavior.

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 covers the parameter with a description. The description adds 'matched on keywords/genres', explaining the similarity logic beyond the schema, which provides additional meaning.

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 action 'Get movies similar' and specifies matching on keywords/genres, distinguishing it from siblings like 'get_recommendations' which may use different criteria.

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

Usage Guidelines3/5

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

The description implies use for similarity-based queries but does not explicitly say when to use versus alternatives like 'get_recommendations' or 'discover_movies'. No guidance on when not to use.

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/AmeliaMiddleton/Mcp1testtypescript'

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