Skip to main content
Glama
panther-labs

Panther MCP Server

Official

get_global_helper

Read-only

Retrieve detailed information about a Panther global helper by ID, including Python body code and usage details for security monitoring and detection rules.

Instructions

Get detailed information about a Panther global helper by ID

Returns complete global helper information including Python body code and usage details.

Permissions:{'all_of': ['View Rules']}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
helper_idYesThe ID of the global helper to fetch

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_global_helper' tool, including @mcp_tool registration decorator, input schema via Pydantic Annotated Field, and the core logic to fetch global helper details from Panther API via REST client.
    @mcp_tool(
        annotations={
            "permissions": all_perms(Permission.RULE_READ),
            "readOnlyHint": True,
        }
    )
    async def get_global_helper(
        helper_id: Annotated[
            str,
            Field(
                description="The ID of the global helper to fetch",
                examples=["MyGlobalHelper", "AWSUtilities", "CrowdStrikeHelpers"],
            ),
        ],
    ) -> dict[str, Any]:
        """Get detailed information about a Panther global helper by ID
    
        Returns complete global helper information including Python body code and usage details.
        """
        logger.info(f"Fetching global helper details for helper ID: {helper_id}")
    
        try:
            async with get_rest_client() as client:
                # Allow 404 as a valid response to handle not found case
                result, status = await client.get(
                    f"/globals/{helper_id}", expected_codes=[200, 404]
                )
    
                if status == 404:
                    logger.warning(f"No global helper found with ID: {helper_id}")
                    return {
                        "success": False,
                        "message": f"No global helper found with ID: {helper_id}",
                    }
    
            logger.info(
                f"Successfully retrieved global helper details for helper ID: {helper_id}"
            )
            return {"success": True, "global_helper": result}
        except Exception as e:
            logger.error(f"Failed to get global helper details: {str(e)}")
            return {
                "success": False,
                "message": f"Failed to get global helper details: {str(e)}",
            }
Behavior4/5

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

Annotations provide readOnlyHint=true, and the description doesn't contradict this. It adds valuable context beyond annotations: it specifies the return content ('complete global helper information including Python body code and usage details') and includes permissions requirements ('Permissions:{'all_of': ['View Rules']}'), which are not covered by annotations. However, it doesn't mention rate limits or other behavioral traits.

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 appropriately sized with three sentences: purpose, return details, and permissions. It's front-loaded with the core purpose, and each sentence adds value (return specifics and permissions). Minor improvement could be merging sentences for tighter flow, but it's efficient with zero waste.

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

Completeness5/5

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

Given the tool's simplicity (1 parameter, 100% schema coverage, read-only operation, and an output schema exists), the description is complete. It covers purpose, return content, and permissions, which are sufficient for an AI agent to understand and invoke the tool correctly without needing to explain return values (handled by output schema).

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

Parameters3/5

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

Schema description coverage is 100%, with the helper_id parameter well-documented in the schema. The description adds no additional parameter semantics beyond what the schema provides (e.g., no format details or examples beyond the schema's examples). Baseline 3 is appropriate since the schema does the heavy lifting.

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 specific action ('Get detailed information') and resource ('Panther global helper by ID'), distinguishing it from sibling tools like list_global_helpers (which lists helpers) and other get_* tools that fetch different resources. The verb+resource combination is precise and unambiguous.

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?

The description implies usage when detailed information about a specific global helper is needed, but it doesn't explicitly state when to use this tool versus alternatives like list_global_helpers (for browsing) or other get_* tools. No exclusions or prerequisites are mentioned beyond the permissions 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/panther-labs/mcp-panther'

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