Skip to main content
Glama
ajragusa

perfsonar-mcp

by ajragusa

schedule_rtt_test

Schedule network latency tests by configuring ping measurements to a destination host using pScheduler.

Instructions

Schedule an RTT (ping) test using pScheduler.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
destYesDestination host
countNoNumber of pings

Implementation Reference

  • The core implementation of the RTT test scheduling logic, which interacts with the pScheduler service.
    async def schedule_rtt_test(
        self, dest: str, count: int = 10, slip: str = "PT10M"
    ) -> PSchedulerTaskResponse:
        """
        Schedule an RTT (round-trip time) test
    
        Args:
            dest: Destination host
            count: Number of pings
            slip: Schedule slip time in ISO 8601 format (e.g., PT10M for 10 minutes)
    
        Returns:
            Task response
        """
        logger.info(f"Scheduling RTT test to {dest} ({count} pings)")
    
        # For RTT tests, schedule on the destination since it measures from local to dest
        scheduler_url = f"https://{dest}/pscheduler"
        logger.info(f"Using pScheduler at: {scheduler_url}")
    
        test_spec = RTTTestSpec(dest=dest, count=count)
    
        task_request = PSchedulerTaskRequest(
            test=PSchedulerTestSpec(type="rtt", spec=test_spec.model_dump(exclude_none=True)),
            schedule={"slip": slip},
        )
    
        # Create a temporary client for this specific scheduler
        client = PSchedulerClient(scheduler_url)
        try:
            return await client.create_task(task_request)
  • The MCP-exposed wrapper function for scheduling RTT tests.
    async def schedule_rtt_test(
        dest: str,
        count: int = 10,
        slip: str = "PT10M",
    ) -> str:
        """Schedule an RTT (ping) test using pScheduler.
    
        Args:
            dest: Destination host for the test
            count: Number of pings (default: 10)
            slip: Schedule slip time in ISO 8601 format (e.g., 'PT10M' for 10 minutes)
    
        Returns:
            JSON string with test details including run URL for status checks
        """
        result = await pscheduler_client.schedule_rtt_test(dest, count, slip)
        return json.dumps(result.model_dump(), indent=2)
  • Registration of the schedule_rtt_test tool in the MCP server.
    Tool(
        name="schedule_rtt_test",
        description="Schedule an RTT (ping) test using pScheduler.",
        inputSchema={
            "type": "object",
            "properties": {
                "dest": {"type": "string", "description": "Destination host"},
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Schedule an RTT (ping) test', implying a write/mutation operation that initiates something, but doesn't cover permissions, side effects, response format, or any operational details like rate limits or idempotency, which are critical for a scheduling tool.

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 with zero waste—it directly states the tool's purpose without unnecessary words or repetition, making it highly concise and well-structured.

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 the complexity of a scheduling tool with no annotations and no output schema, the description is incomplete. It lacks information on what happens after scheduling (e.g., returns a test ID, status), error handling, or dependencies, leaving significant gaps for the agent to understand the tool's full context.

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%, so the schema fully documents the two parameters ('dest' and 'count'). The description adds no additional meaning beyond what's in the schema, such as examples or constraints, but since the schema is complete, this meets the baseline for adequate parameter semantics.

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 ('Schedule') and resource ('RTT (ping) test using pScheduler'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'schedule_latency_test' or 'schedule_throughput_test', which would require mentioning what makes RTT/ping distinct from those other scheduling operations.

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. With siblings like 'schedule_latency_test' and 'schedule_throughput_test', there's no indication of whether RTT is a subset, complementary, or different type of test, leaving the agent without context for tool selection.

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/ajragusa/perfsonar-mcp'

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