Skip to main content
Glama
ajragusa

perfsonar-mcp

by ajragusa

get_test_result

Retrieve completed network performance test results from perfSONAR to analyze throughput, latency, and packet loss measurements.

Instructions

Get result of a completed pScheduler test.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
runUrlYesRun URL from test scheduling

Implementation Reference

  • The 'get_test_result' tool implementation in 'fastmcp_server.py' which uses the 'pscheduler_client' to fetch test results.
    async def get_test_result(runUrl: str) -> str:
        """Get result of a completed pScheduler test.
    
        Args:
            runUrl: Run URL from test scheduling response
    
        Returns:
            JSON string with test results, or message if test not completed yet
        """
        result = await pscheduler_client.get_result(runUrl)
        if result:
            return json.dumps(result.model_dump(), indent=2)
        else:
            return json.dumps({"message": "Test not completed yet"})
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as authentication needs, rate limits, error handling, or what format the result returns (e.g., JSON, raw data). This leaves significant gaps for an agent to use it correctly.

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's appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary details.

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 doesn't explain what the result looks like (e.g., data format, structure), error cases, or dependencies on other tools like scheduling tests. For a tool with one parameter but critical behavioral unknowns, this is inadequate.

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 already documents the 'runUrl' parameter fully. The description doesn't add any meaning beyond what the schema provides, such as examples or context for the run URL. Baseline 3 is appropriate as the schema does the heavy lifting.

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 result') and resource ('completed pScheduler test'), making the purpose understandable. It distinguishes from siblings like 'get_test_status' by focusing on results rather than status, though it doesn't explicitly mention this distinction.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_test_status' or other measurement tools. The description implies usage for completed tests but doesn't specify prerequisites, error conditions, or when not to use it.

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