Skip to main content
Glama
richarda23

Edinburgh Festivals MCP Server

by richarda23

edinburgh_festival_venue_routes

Calculate walking routes between Edinburgh festival venues to help plan event attendance and navigate festival locations efficiently.

Instructions

Calculate route between venues

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originYes
destinationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:51-63 (handler)
    The handler function decorated with @mcp.tool, implementing the tool logic by using Google Maps CLI to fetch walking directions between two venues, with error handling for missing API key.
    @mcp.tool(description="Calculate route between venues")
    def edinburgh_festival_venue_routes(origin: str, destination: str) -> Dict:
        """
        Calculates the route between two venues.
        :param origin: The starting venue
        :param destination: The destination venue.
        :return: A dictionary containing route information:.
        """
        gmaps_cli = gmaps.GMAPS()
        if not gmaps_cli.enabled:
            return {"error": "Google Maps API key is not set. This tool is not available."}
        directions = gmaps_cli.get_directions(origin, destination, mode="walking")
        return directions
  • main.py:51-51 (registration)
    The @mcp.tool decorator registers the edinburgh_festival_venue_routes function as an MCP tool.
    @mcp.tool(description="Calculate route between venues")
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool calculates routes but doesn't describe what the output includes (e.g., distance, time, directions), whether it's real-time or cached, any rate limits, or authentication needs. This leaves significant gaps for a routing 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 a single, clear sentence with no wasted words. It's front-loaded and efficiently communicates the core purpose without unnecessary elaboration, making it easy to parse 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 has an output schema (which should cover return values), the description's job is lighter. However, with no annotations and low schema coverage, it still lacks details on behavioral aspects like route type or constraints. It's minimally adequate but could be more informative for a routing operation.

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

Parameters2/5

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

The schema description coverage is 0%, so the description must compensate. It mentions 'venues' but doesn't clarify what format the origin and destination parameters should be in (e.g., venue names, IDs, addresses) or provide examples. This adds minimal value beyond the schema's basic property names.

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 'Calculate route between venues' clearly states the action (calculate route) and resource (venues), which is adequate. However, it doesn't specify what type of route (walking, driving, etc.) or distinguish it from potential sibling tools like 'edinburgh_festival_venues' which might provide venue information rather than routing.

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 the sibling tools 'edinburgh_festival_events' or 'edinburgh_festival_venues', nor does it specify prerequisites like needing venue names from another tool first. Usage context is implied but not explicit.

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/richarda23/edfest-mcp'

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