Skip to main content
Glama
intruder-io

intruder-mcp

Official

list_scan_schedules

Retrieve all scan schedules from your Intruder account, including complete details for each.

Instructions

List all scan schedules in the Intruder account, including the full record for each.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler that lists all scan schedules by calling the API client and formatting each schedule's details (id, name, schedule_period, status, timestamps, targets, tags, etc.) into a readable string.
    @mcp.tool()
    async def list_scan_schedules() -> str:
        """
        List all scan schedules in the Intruder account, including the full record for each.
        """
        response = api.list_scan_schedules()
        if not response.results:
            return "No scan schedules found."
        blocks = []
        for s in response.results:
            block = [
                f"{s.id} - {s.name}",
                f"  schedule_period: {s.schedule_period}",
                f"  status: {s.status}",
                f"  first_scan_time: {s.first_scan_time}",
                f"  next_scan_date: {s.next_scan_date}",
                f"  throttled: {s.throttled}",
                f"  web_ports_only: {s.web_ports_only}",
                f"  upload_to_drata: {s.upload_to_drata}",
                f"  upload_to_vanta: {s.upload_to_vanta}",
                f"  latest_scan_id: {s.latest_scan_id}",
                f"  latest_scan_status: {s.latest_scan_status}",
                f"  last_scan_start_time: {s.last_scan_start_time}",
                f"  last_scan_end_time: {s.last_scan_end_time}",
                f"  targets: {', '.join(map(str, s.targets)) if s.targets else '(none)'}",
                f"  target_tags: {', '.join(s.target_tags) if s.target_tags else '(none)'}",
            ]
            blocks.append("\n".join(block))
        return "\n\n".join(blocks)
  • Tool registration using @mcp.tool() decorator, registering 'list_scan_schedules' as an MCP tool on the FastMCP server instance.
    @mcp.tool()
    async def list_scan_schedules() -> str:
  • API client method that performs the actual HTTP GET request to /v1/scans/schedules/ and deserializes the response into an AssessmentScheduleListResponse.
    def list_scan_schedules(self) -> AssessmentScheduleListResponse:
        return AssessmentScheduleListResponse(**self.client.get(f"{self.base_url}/scans/schedules/").json())
  • Response schema model containing count and results list of AssessmentScheduleList objects.
    class AssessmentScheduleListResponse(BaseModel):
        count: int
        results: List[AssessmentScheduleList]
  • Schema for individual scan schedule items with fields like id, name, schedule_period, status, timestamps, targets, tags, and upload flags.
    class AssessmentScheduleList(BaseModel):
        id: int
        name: str
        schedule_period: SchedulePeriodEnum
        first_scan_time: datetime
        next_scan_date: datetime
        status: str
        throttled: bool
        web_ports_only: bool
        latest_scan_id: Optional[int] = None
        latest_scan_status: Optional[str] = None
        last_scan_start_time: Optional[datetime] = None
        last_scan_end_time: Optional[datetime] = None
        targets: List[int] = []
        target_tags: List[str] = []
        upload_to_drata: bool
        upload_to_vanta: bool
Behavior2/5

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

No annotations are present, so the description carries full burden to disclose behavioral traits. It does not mention read-only nature (though implicit), potential pagination, authentication requirements, rate limits, or performance implications. This is insufficient for a safe agent invocation.

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, direct sentence with no extraneous words. It is front-loaded and efficient.

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?

Given no parameters and the presence of an output schema, the description is adequate but minimal. It misses behavioral context such as whether the list is paginated, the order of results, or any side effects. Still, it covers the basic purpose.

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 tool has zero parameters, and schema coverage is 100% (vacuous). The description does not need to add parameter-level information. Baseline score of 4 is appropriate.

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 uses a specific verb ('List') and resource ('scan schedules'), includes scope ('all in the Intruder account'), and mentions completeness ('including the full record'). This clearly differentiates it from sibling tools like create_scan_schedule or delete_scan_schedule.

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 or when not to use this tool. The name and description imply it is for listing, but an agent receives no clarification about prerequisites, alternatives, or context where other tools might be preferred.

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