Skip to main content
Glama
code4mk

Cox's Bazar AI Itinerary MCP Server

get_activity_suggestions

Generate personalized activity recommendations for Cox's Bazar based on current temperature and time of day to optimize your travel itinerary.

Instructions

Suggest activities based on temperature and time of day.

Args: temperature: Temperature in Celsius time_of_day: "morning", "afternoon", or "evening"

Returns: List of suggested activities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
temperatureYes
time_of_dayNoafternoon

Implementation Reference

  • MCP tool registration for get_activity_suggestions with name and description.
    @mcp.tool(
        name="get_activity_suggestions",
        description="suggest activities based on temperature and time of day",
    )
  • Handler function that wraps the helper and executes the tool logic by calling the imported get_suggestions.
    async def get_activity_suggestions(temperature: float, time_of_day: str = "afternoon") -> list[str]:
        """
        Suggest activities based on temperature and time of day.
        
        Args:
            temperature: Temperature in Celsius
            time_of_day: "morning", "afternoon", or "evening"
        
        Returns:
            List of suggested activities
        """
        return get_suggestions(temperature, time_of_day)
  • Core helper function implementing the activity suggestion logic with conditional lists based on temperature and time of day.
    def get_activity_suggestions(temperature: float, time_of_day: str = "afternoon") -> List[str]:
        """
        Suggest activities based on temperature and time of day.
        
        Args:
            temperature: Temperature in Celsius
            time_of_day: "morning", "afternoon", or "evening"
        
        Returns:
            List of suggested activities
        """
        suggestions = []
        
        if time_of_day == "morning":
            if temperature < 28:
                suggestions = [
                    "Beach walk and photography",
                    "Visit Himchari National Park",
                    "Sunrise at Laboni Beach",
                    "Morning yoga on the beach"
                ]
            else:
                suggestions = [
                    "Early morning swim",
                    "Sunrise boat ride",
                    "Visit Inani Beach",
                    "Morning market exploration"
                ]
        
        elif time_of_day == "afternoon":
            if temperature < 30:
                suggestions = [
                    "Visit Aggameda Khyang monastery",
                    "Explore Ramu Buddhist Village",
                    "Maheshkhali Island tour",
                    "Marine Drive scenic route"
                ]
            else:
                suggestions = [
                    "Indoor activities - shopping at local markets",
                    "Visit Bangabandhu Safari Park",
                    "Relax at beach resorts",
                    "Water sports activities"
                ]
        
        else:  # evening
            suggestions = [
                "Sunset at Sugandha Beach",
                "Seafood dinner at local restaurants",
                "Beach bonfire",
                "Night market shopping",
                "Cultural performances"
            ]
        
        return suggestions
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 of suggested activities,' which hints at read-only behavior, but it does not disclose any traits like whether it's safe, if there are rate limits, authentication needs, or how the suggestions are generated. The description is minimal and lacks critical behavioral context for a tool with no annotations.

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 appropriately sized and front-loaded, with a clear purpose statement followed by structured sections for 'Args' and 'Returns.' Every sentence earns its place by providing essential information without waste, making it easy to scan and understand quickly.

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 (2 parameters, no annotations, no output schema), the description is somewhat complete but has gaps. It covers the purpose and parameters well, but lacks usage guidelines and behavioral transparency. Without an output schema, it minimally describes returns, but more context on behavior would improve completeness for effective agent use.

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 significant meaning beyond the input schema, which has 0% description coverage. It explains that 'temperature' is in Celsius and 'time_of_day' can be 'morning', 'afternoon', or 'evening', providing semantic context that the schema lacks. Since there are only 2 parameters and the description compensates well for the low schema coverage, this earns a high score.

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: 'Suggest activities based on temperature and time of day.' It specifies the verb ('suggest') and resources ('activities'), and while it doesn't explicitly differentiate from the sibling tool 'cox_ai_itinerary', the purpose is specific enough to understand its function. It's not a tautology since it elaborates beyond just the name.

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 mentions the sibling tool 'cox_ai_itinerary' in the context, but the description itself does not indicate any relationship, exclusions, or prerequisites. Usage is implied only by the parameters, with no explicit context or alternatives stated.

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/code4mk/mcp-boilerplate'

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