Skip to main content
Glama

status

Review which applications are permitted and if dangerous command blocking is active to ensure safe AppleScript operations.

Instructions

Returns the list of allowed apps and whether dangerous command blocking is enabled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'status' tool handler function. Decorated with @mcp.tool(), it returns a dict with 'allowed_apps' (display-friendly list of allowed apps) and 'block_dangerous' (boolean indicating if dangerous pattern blocking is enabled). It delegates to helper functions get_allowed_apps() and is_dangerous_blocking_enabled().
    @mcp.tool()
    async def status() -> dict:
        """Returns the list of allowed apps and whether dangerous command blocking is enabled."""
        allowed_apps = get_allowed_apps()
    
        if "*" in allowed_apps:
            apps_display = "all applications"
        elif not allowed_apps:
            apps_display = "none (all blocked)"
        else:
            apps_display = allowed_apps
    
        return {
            "allowed_apps": apps_display,
            "block_dangerous": is_dangerous_blocking_enabled(),
        }
  • The 'status' tool is registered via the @mcp.tool() decorator on line 13, which registers the async function as an MCP tool on the FastMCP instance named 'mcp'.
    @mcp.tool()
    async def status() -> dict:
  • Helper function get_allowed_apps() reads the ALLOWED_APPS environment variable, returning a list of allowed app names (or ['*'] for all, or [] for none).
    def get_allowed_apps() -> list[str]:
        """
        Get the list of allowed applications from environment variable.
        """
        # Default to "*" if not set
        allowed = os.getenv("ALLOWED_APPS", "*").strip()
    
        # Empty string means explicit lockdown
        if not allowed:
            return []
    
        # Wildcard means allow all
        if allowed == "*":
            return ["*"]
    
        # Parse comma-separated list, normalize to title case for AppleScript
        return [app.strip().title() for app in allowed.split(",") if app.strip()]
  • Helper function is_dangerous_blocking_enabled() reads the BLOCK_DANGEROUS environment variable (defaulting to 'true') and returns a boolean.
    def is_dangerous_blocking_enabled() -> bool:
        """
        Check if dangerous pattern blocking is enabled.
        """
        value = os.getenv("BLOCK_DANGEROUS", "true").lower()
        return value in ("true", "1", "yes", "on")
Behavior4/5

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

Despite no annotations, the description indicates a read-only operation ('Returns'). It does not disclose permissions or potential side effects, but for a status query with no parameters, the behavioral disclosure is adequate.

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?

A single sentence that is concise and front-loaded with the action and key outputs. No extraneous information.

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?

Given the absence of parameters and output schema, the description effectively explains what the tool returns. It covers the main outputs, though the format of the list or boolean is not specified, which is acceptable for this simplicity.

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 exist (input schema empty, 100% coverage by default). The description does not need to explain parameters, so the baseline score of 4 applies.

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?

The description clearly states the tool returns 'the list of allowed apps' and 'whether dangerous command blocking is enabled', specifying both the action (returns) and the resources. This is specific and distinguishes from the sibling tool 'run_applescript'.

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 guidance on when to use this tool versus alternatives. The sibling is 'run_applescript', which is a different function, so usage context is implied as a status check, but no when-not or conditional advice is provided.

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/pietz/mcp-applescript'

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