Skip to main content
Glama
GongRzhe

Terminal Controller for MCP

get_current_directory

Retrieve the current working directory path to identify your location in the file system for navigation and command execution.

Instructions

Get current working directory

Returns:
    Path of current working directory

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool is registered via the @mcp.tool() decorator on line 170, which automatically registers it with the FastMCP server.
    @mcp.tool()
    async def get_current_directory() -> str:
  • The handler function 'get_current_directory' is an async function that returns the current working directory by calling os.getcwd().
    async def get_current_directory() -> str:
        """
        Get current working directory
        
        Returns:
            Path of current working directory
        """
        return os.getcwd()
  • The function signature and docstring define the schema: no parameters, returns a string with the path of the current working directory.
    async def get_current_directory() -> str:
        """
        Get current working directory
        
        Returns:
            Path of current working directory
        """
Behavior3/5

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

No annotations provided. Description is minimal but adequately conveys the read-only, safe nature of the operation. Does not mention error conditions or dependencies, but acceptable for a trivial 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?

Extremely concise: two lines, no wasted words. Front-loaded with the key purpose.

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

Completeness4/5

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

Adequate for a parameterless tool without output schema. States purpose and return value. Could mention error cases, but not critical.

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?

No parameters in schema (100% coverage). Description adds value by explicitly stating return value, which is not part of input schema. Baseline for 0 params is 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states action ('Get current working directory') and return value ('Path of current working directory'). Distinct from siblings like change_directory and list_directory.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit usage guidance; does not specify when to use this tool over alternatives. For a simple getter, context is somewhat implied but could be improved.

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/GongRzhe/terminal-controller-mcp'

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