perfsonar-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PERFSONAR_HOST | Yes | Required host address of the perfSONAR server (e.g., perfsonar.example.com). | |
| PSCHEDULER_URL | No | Optional URL for the pScheduler service. | |
| PYTHONLOGLEVEL | No | Optional log level for the server (e.g., DEBUG, INFO, WARNING, ERROR). | |
| LOOKUP_SERVICE_URL | No | Optional URL for the perfSONAR Lookup Service (default: https://lookup.perfsonar.net/lookup). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_measurementsC | Query perfSONAR measurements with optional filters. Returns metadata about available measurements. |
| get_measurement_dataC | Get raw time-series data for a specific measurement. |
| get_throughputC | Get throughput measurements between source and destination. |
| get_latencyC | Get latency/delay measurements between source and destination. |
| get_packet_lossC | Get packet loss measurements between source and destination. |
| get_available_event_typesC | Get all available event types in the archive. |
| lookup_testpointsC | Find perfSONAR testpoints using the lookup service. |
| find_pscheduler_servicesC | Find pScheduler services for running tests. |
| schedule_throughput_testC | Schedule a throughput test using pScheduler. |
| schedule_latency_testC | Schedule a latency test using pScheduler. |
| schedule_rtt_testC | Schedule an RTT (ping) test using pScheduler. |
| get_test_statusC | Get status of a pScheduler test run. |
| get_test_resultC | Get result of a completed pScheduler test. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| perfSONAR Archive | Main perfSONAR measurement archive |
TDQS
Scored across 13 tools
Most tools have distinct purposes, but there is some potential confusion between get_latency/get_packet_loss/get_throughput (all measurement retrievals) and schedule_latency_test/schedule_throughput_test (test scheduling). The descriptions clarify the action vs. scheduling distinction, but the similar naming could cause misselection.
All tools follow a consistent verb_noun pattern with snake_case throughout. The naming is highly predictable, using verbs like get, find, query, schedule, and lookup consistently across the toolset.
With 13 tools, this is well-scoped for a perfSONAR monitoring and testing server. The count is appropriate, covering service discovery, test scheduling, measurement retrieval, and data querying without being overwhelming.
The toolset provides strong coverage for the perfSONAR domain, including test scheduling, status/result retrieval, and measurement queries. A minor gap is the lack of tools for managing or canceling scheduled tests, which could limit workflow completeness.