Skip to main content
Glama
intruder-io

intruder-mcp

Official

get_user

Retrieve the authenticated user identity for the Intruder API to verify current session permissions and access rights.

Instructions

Get the current user of the Intruder API that we are authenticated as

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'get_user' tool. Decorated with @mcp.tool() which registers it with the MCP server. Retrieves the authenticated user from the Intruder API health check and returns it as a string.
    @mcp.tool()
    async def get_user() -> str:
        """Get the current user of the Intruder API that we are authenticated as"""
        health = api.get_health()
        return health.authenticated_as
  • The @mcp.tool() decorator registers the get_user function as an MCP tool.
    @mcp.tool()
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the authentication requirement ('authenticated as'), which is useful behavioral context. However, it doesn't mention rate limits, error conditions, or response format details. The description doesn't contradict any annotations.

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?

Single sentence, front-loaded with the core purpose. No wasted words, and every part of the description adds value (specifying API context and authentication). Efficiently structured.

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

Completeness3/5

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

For a simple 0-parameter tool with no output schema, the description covers the basic purpose and authentication context adequately. However, without annotations or output schema, it could benefit from more behavioral details like response format or error handling, but it's minimally sufficient.

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?

There are 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing on the tool's purpose instead. Baseline for 0 parameters is 4.

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 verb 'Get' and the resource 'current user of the Intruder API', specifying it's the authenticated user. It distinguishes from siblings like get_scan or get_status by focusing on user identity. However, it doesn't explicitly differentiate from potential user-related tools not present in the sibling list.

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 context ('authenticated as') but doesn't provide explicit guidance on when to use this versus alternatives. No when-not-to-use scenarios or prerequisites are mentioned, though the authentication context is helpful.

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