Skip to main content
Glama
intruder-io

intruder-mcp

Official

get_status

Check the operational status of the Intruder API to verify connectivity and service availability for security testing workflows.

Instructions

Get the status of the Intruder API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_status' MCP tool, registered via the @mcp.tool() decorator. It calls the API client's get_health method and returns the status string.
    @mcp.tool()
    async def get_status() -> str:
        """Get the status of the Intruder API"""
        health = api.get_health()
        return health.status
  • Supporting method in the IntruderAPI class that performs the HTTP request to retrieve the API health status and parses it using the Health Pydantic model.
    def get_health(self) -> Health:
        return Health(**self.client.get(f"{self.base_url}/health/").json())
  • Pydantic schema/model for the API health response, which includes the 'status' field returned by the get_status tool.
    status: str = Field(..., description="API health status")
    authenticated_as: str = Field(..., format="email")
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention what the status includes (e.g., uptime, rate limits, authentication needs), response format, or potential side effects, which is inadequate for a tool with zero annotation coverage.

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 is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 no annotations and no output schema, the description is incomplete. It lacks details on what the status check returns, how to interpret results, or any behavioral context, which is insufficient for a tool that might involve API health or operational state.

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 no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it doesn't compensate for any gaps since there are none. Baseline 4 is given as it meets the requirement for zero parameters.

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 action ('Get') and target ('status of the Intruder API'), making the purpose understandable. However, it doesn't differentiate from sibling tools that also retrieve information (like get_scan, get_scanner_output, get_user), so it's not fully specific about what makes this status check unique.

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, context for checking API status, or how it differs from other get_* tools in the sibling list, leaving the agent without usage direction.

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/intruder-io/intruder-mcp'

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