Space Weather Data MCP Server

list_known_paths

Orient yourself on the SWPC data server by obtaining a curated map of notable paths and files, making initial exploration easier.

Instructions

Return a curated map of notable paths and files on the SWPC data server.

Use this tool first to orient yourself before calling list_directory or fetch_file. The returned map groups paths by top-level directory and highlights commonly useful files.

Returns: A dict describing the server layout and selected files of interest.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_known_paths"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.7/5.0

Behavior4/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. It discloses that the tool returns a curated, grouped map and highlights useful files, which conveys read-only behavior and output structure. It stops short of explicitly stating 'no side effects' or auth requirements, but for a listing/orientation tool this is adequate.

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 concise and well-structured: a clear one-sentence purpose, a usage directive, and a brief Returns section. Every sentence adds value without redundancy or unnecessary length.

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

Completeness5/5

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

Given the tool has no parameters and an output schema is present, the description fully covers what an agent needs to select and invoke it correctly. It includes purpose, usage context, and output format, making it complete for this simple tool.

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 the description's baseline for parameter semantics is therefore 4. There is nothing to add beyond the schema, and the description appropriately focuses on purpose and output rather than parameter details.

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 phrase 'Return a curated map of notable paths and files' and identifies the resource 'SWPC data server'. It clearly distinguishes the tool from siblings by stating it is a preliminary orientation tool, referencing list_directory and fetch_file as subsequent steps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance is provided: 'Use this tool first to orient yourself before calling list_directory or fetch_file.' This tells the agent exactly when to use the tool and names the alternatives, making tool selection unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server