Skip to main content
Glama
hi5d
by hi5d

get_now_showing

Find movies currently playing in theaters near you by entering your city or ZIP code. Get a list of showtimes and available films for AMC Theatres.

Instructions

Returns a list of movies currently showing in a given city or ZIP code.

Args: location: City, state or ZIP code (e.g., "Boston, MA")

Returns: JSON string with list of movies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Registers the get_now_showing tool with name, description, and input schema requiring 'location' parameter.
    Tool(
        name="get_now_showing",
        description="Returns a list of movies currently showing in a given city or ZIP code",
        inputSchema={
            "type": "object",
            "properties": {
                "location": {"type": "string", "description": "City, state or ZIP code"}
            },
            "required": ["location"]
        }
    ),
  • Core handler function for the get_now_showing tool. Extracts location from arguments, loads mock movie data, and returns JSON-formatted list of up to 10 movies currently showing.
    async def _get_now_showing(self, args: Dict[str, Any]) -> CallToolResult:
        """Get movies currently showing in a location"""
        location = args.get("location", "")
        
        # Filter movies by location (simplified - match any theater in the area)
        showing_movies = []
        for movie in self.movies.values():
            # Simple mock logic - show all movies for any location
            movie_data = {
                "movie_id": movie.movie_id,
                "title": movie.title,
                "rating": movie.rating,
                "duration": movie.duration,
                "genre": movie.genre,
                "description": movie.description
            }
            showing_movies.append(movie_data)
        
        result = {
            "location": location,
            "movies": showing_movies[:10]  # Limit to 10 movies
        }
        
        return CallToolResult(
            content=[TextContent(type="text", text=json.dumps(result, indent=2))]
        )
  • FastMCP implementation of the get_now_showing tool handler, decorated for automatic registration, delegates to internal helper.
    def get_now_showing(location: str) -> str:
        """
        Returns a list of movies currently showing in a given city or ZIP code.
        
        Args:
            location: City, state or ZIP code (e.g., "Boston, MA")
        
        Returns:
            JSON string with list of movies
        """
        return _get_now_showing(location)
  • Helper function containing the shared logic for retrieving and formatting movies currently showing for a location (identical to server.py implementation).
    def _get_now_showing(location: str) -> str:
        """
        Returns a list of movies currently showing in a given city or ZIP code.
        
        Args:
            location: City, state or ZIP code (e.g., "Boston, MA")
        
        Returns:
            JSON string with list of movies
        """
        showing_movies = []
        for movie in movies.values():
            movie_data = {
                "movie_id": movie.movie_id,
                "title": movie.title,
                "rating": movie.rating,
                "duration": movie.duration,
                "genre": movie.genre,
                "description": movie.description
            }
            showing_movies.append(movie_data)
        
        result = {
            "location": location,
            "movies": showing_movies[:10]
        }
        
        return json.dumps(result, indent=2)
  • FastMCP registration of the get_now_showing tool via @mcp.tool() decorator on the handler function.
    def get_now_showing(location: str) -> str:
        """
        Returns a list of movies currently showing in a given city or ZIP code.
        
        Args:
            location: City, state or ZIP code (e.g., "Boston, MA")
        
        Returns:
            JSON string with list of movies
        """
        return _get_now_showing(location)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool returns a list, but doesn't describe traits like error handling, rate limits, authentication needs, or whether it's a read-only operation. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 appropriately sized and front-loaded, with the core purpose stated first, followed by structured sections for Args and Returns. Each sentence earns its place, though the 'Returns' section could be slightly more detailed given the lack of output schema description in this context.

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 the tool's low complexity (1 parameter, no nested objects) and the presence of an output schema, the description is minimally adequate. However, with no annotations and incomplete behavioral details, it doesn't fully compensate for the structured data gaps. The output schema existence reduces the need to explain return values, but more context on usage and behavior would improve completeness.

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 description adds meaningful context for the single parameter 'location', specifying it as 'City, state or ZIP code (e.g., "Boston, MA")'. Since schema description coverage is 0% and there's only one parameter, this compensates well, providing clear examples and format guidance beyond the basic schema type.

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 the tool's purpose: 'Returns a list of movies currently showing in a given city or ZIP code.' This specifies the verb ('returns'), resource ('list of movies'), and scope ('currently showing in a given city or ZIP code'). However, it doesn't explicitly differentiate from sibling tools like 'get_showtimes' or 'get_recommendations', which might have overlapping functionality.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_showtimes' or 'get_recommendations', nor does it specify prerequisites, exclusions, or contextual cues for usage. The agent must infer usage based on the purpose alone.

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/hi5d/amc-mcp'

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