Skip to main content
Glama
yonaka15
by yonaka15

pyodide_get-mount-points

List mounted directories in Pyodide to manage file system access for Python code execution by LLMs.

Instructions

List mounted directories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core implementation of the pyodide_get-mount-points tool that retrieves the list of mounted directories from the internal mountPoints Map and formats the response.
    async getMountPoints() {
      if (!this.pyodide) {
        return formatCallToolError("Pyodide not initialized");
      }
    
      try {
        const mountPoints = Array.from(this.mountPoints.entries()).map(
          ([name, config]) => ({
            name,
            hostPath: config.hostPath,
            mountPoint: config.mountPoint,
          })
        );
        return formatCallToolSuccess(JSON.stringify(mountPoints, null, 2));
      } catch (error) {
        return formatCallToolError(error);
      }
    }
  • MCP server request handler switch case that dispatches the pyodide_get-mount-points tool call to PyodideManager.getMountPoints().
    case "pyodide_get-mount-points": {
      const results = await pyodideManager.getMountPoints();
      return results;
    }
  • Tool schema and metadata definition, specifying the name, description, and empty input schema (no arguments required).
    export const GET_MOUNT_POINTS_TOOL: Tool = {
      name: "pyodide_get-mount-points",
      description: "List mounted directories",
      inputSchema: {
        type: "object",
        properties: {},
      },
    };
  • Tool registration in the TOOLS array exported for the ListTools MCP request handler.
    const TOOLS: Tool[] = [
      tools.EXECUTE_PYTHON_TOOL,
      tools.INSTALL_PYTHON_PACKAGES_TOOL,
      tools.GET_MOUNT_POINTS_TOOL,
      tools.LIST_MOUNTED_DIRECTORY_TOOL,
      tools.READ_IMAGE_TOOL,
    ];
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 lists mounted directories but doesn't describe what 'mounted' means in this context, the format of the output, whether it's a read-only operation, or any performance or error-handling traits. This leaves significant gaps for a tool that might interact with a filesystem.

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 'List mounted directories' is a single, efficient sentence that front-loads the core purpose with zero waste. It's appropriately sized for a simple tool with no parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'mounted' entails in this Pyodide context, the return format (e.g., list of paths, JSON structure), or how it differs from 'pyodide_list-mounted-directory'. For a tool that might involve filesystem operations, more context is needed.

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 input schema has 0 parameters with 100% coverage, so the schema fully documents the absence of inputs. The description doesn't add parameter-specific information, but since there are no parameters, a baseline score of 4 is appropriate as no compensation is needed for missing details.

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 'List mounted directories' clearly states the verb ('List') and resource ('mounted directories'), making the tool's purpose immediately understandable. However, it doesn't differentiate from the sibling tool 'pyodide_list-mounted-directory', which appears to have a similar function, so it doesn't achieve full sibling differentiation.

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 like 'pyodide_list-mounted-directory'. There's no mention of prerequisites, context, or exclusions, leaving the agent with no usage instructions beyond the basic purpose.

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/yonaka15/mcp-pyodide'

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