Skip to main content
Glama
zahlenhelfer

movieplexx-mcp

by zahlenhelfer

list_films

Get a complete film list or filter to only films currently showing with upcoming performances.

Instructions

List all known films. With only_current, restrict to films with an upcoming performance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
only_currentNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It states it lists films (read-only), but lacks important details such as whether pagination is used, ordering, or any side effects. This is minimal for a listing tool.

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 two sentences, front-loaded with the main purpose, and contains no extraneous information. Every word adds value.

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 simple tool with one parameter and an output schema, the description is adequate but misses contextual details such as the default value of 'only_current' (true) and whether the list is paginated or sorted. The output schema may fill some gaps, but the description could be more complete.

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?

The schema has 0% description coverage for the only parameter. The description adds clear meaning: 'With only_current, restrict to films with an upcoming performance,' which explains the boolean parameter's effect.

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 clearly states 'List all known films' which is a specific verb and resource. It distinguishes from sibling tools like 'search_films' by indicating it's a full listing, but does not explicitly differentiate from 'list_showtimes' or 'get_film'.

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 usage by describing the 'only_current' parameter for filtering to upcoming performances, but it does not provide explicit guidance on when to use this tool vs. alternatives like 'search_films' or when not to use it.

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/zahlenhelfer/movieplexx-mcp'

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