Skip to main content
Glama
vlad-ds

Street View MCP

by vlad-ds

open_image_locally

Open saved Street View images in your default viewer application to examine captured locations and landmarks from virtual tours.

Instructions

Open a saved Street View image in the default application.

Args: filename: The filename of the image to open (must exist in output directory)

Returns: Dict: A status message indicating success or failure

Raises: ValueError: If the file doesn't exist in the output directory

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes

Implementation Reference

  • The core handler function for the 'open_image_locally' tool. Decorated with @mcp.tool() for automatic registration in FastMCP. Validates the image file exists in the output directory, converts to URI, and opens it in the default local application using webbrowser.open(). Returns success status.
    @mcp.tool()
    def open_image_locally(filename: str) -> Dict[str, str]:
        """
        Open a saved Street View image in the default application.
        
        Args:
            filename: The filename of the image to open (must exist in output directory)
            
        Returns:
            Dict: A status message indicating success or failure
            
        Raises:
            ValueError: If the file doesn't exist in the output directory
        """
        # Check if file exists
        image_path = OUTPUT_DIR / filename
        if not image_path.exists():
            raise ValueError(f"Image file '{filename}' does not exist in the output directory")
        
        # Convert to absolute path
        abs_path = image_path.absolute().as_uri()
        
        # Open in local application
        webbrowser.open(abs_path)
        
        return {"status": "success", "message": f"Opened {filename} in default application"}
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool opens files in the default application (implying a system-level action) and raises errors for non-existent files, which is useful behavioral context. However, it lacks details on permissions needed, platform-specific behavior, or what 'success' entails beyond a status message.

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 well-structured with a clear opening sentence followed by Args/Returns/Raises sections. It's appropriately sized for a simple tool, though the 'Dict' return type could be more specific. Every sentence adds value, but the structure is slightly verbose for a single-parameter tool.

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 no output schema, the description covers the basic operation and error case adequately. However, it lacks context about the output directory (where files are saved) and doesn't explain the return value format beyond 'Dict', leaving gaps for the agent to understand the full workflow.

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, but the description compensates well by explaining the 'filename' parameter's purpose ('The filename of the image to open') and constraint ('must exist in output directory'). This adds crucial meaning beyond the bare schema, though it doesn't specify the output directory location or file format expectations.

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 verb ('Open') and resource ('saved Street View image') with specific context ('in the default application'). It distinguishes from siblings like 'get_street_view' (which likely fetches images) by focusing on opening existing files. However, it doesn't explicitly contrast with 'create_html_page' or 'get_metadata'.

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 prerequisites (e.g., that the file must already exist from another operation) or compare with sibling tools like 'get_street_view' for obtaining images. The only implicit context is the file existence requirement.

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/vlad-ds/street-view-mcp'

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