Skip to main content
Glama
miroslawfranek

Open-E JovianDSS REST API Documentation MCP Server

download_edss_documentation

Need EDSS documentation? Get a download link for the entire documentation as a ZIP file.

Instructions

Get download link for EDSS documentation as ZIP file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
downloadNoReturn download information for ZIP file

Implementation Reference

  • index.js:67-79 (registration)
    Tool registration in ListToolsRequestSchema handler. Defines name, description, and input schema for the 'download_edss_documentation' tool.
      name: "download_edss_documentation", 
      description: "Get download link for EDSS documentation as ZIP file",
      inputSchema: {
        type: "object",
        properties: {
          download: {
            type: "boolean",
            default: true,
            description: "Return download information for ZIP file"
          }
        }
      }
    },
  • Input schema for the download_edss_documentation tool. Accepts optional 'download' boolean with default true.
      inputSchema: {
        type: "object",
        properties: {
          download: {
            type: "boolean",
            default: true,
            description: "Return download information for ZIP file"
          }
        }
      }
    },
  • Handler function for download_edss_documentation. Returns JSON with the ZIP download URL (latest version) from legacyDocUrls. Note: the 'download' input arg is accepted but not used in the implementation.
    async downloadDocumentation(args) {
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              zipUrl: this.legacyDocUrls.latestZip,
              description: "Download complete EDSS documentation as ZIP",
              contentType: "application/zip",
              version: "latest"
            }, null, 2)
          }
        ]
      };
    }
  • Legacy URL helper object containing the ZIP download URL used by the downloadDocumentation handler.
    this.legacyDocUrls = {
      latest: "http://dh.lan:777/docs/EDSS/JEFFERSONVILLE/documentation/v4/",
      trunk: "http://dh.lan:777/docs/EDSS/trunk/documentation/v4/",
      latestZip: "http://dh.lan:777/docs/EDSS/JEFFERSONVILLE/documentation/v4/get_doc.php?t=zip"
    };
  • index.js:186-187 (registration)
    Tool call dispatch in CallToolRequestSchema handler. Routes the tool name 'download_edss_documentation' to the downloadDocumentation method.
    case "download_edss_documentation":
      return await this.downloadDocumentation(args);
Behavior2/5

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

No annotations are present, and the description only states the function without disclosing behavioral traits like whether the download link expires, requires authentication, or has side effects.

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?

One concise sentence with no extraneous words, efficiently conveying the tool's purpose.

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?

For a simple tool with one parameter, the description is adequate but could mention the nature of the download link (e.g., direct URL) and any prerequisites.

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?

The schema description coverage is 100% for the single boolean parameter 'download', and the tool description adds no additional meaning beyond what the schema already provides.

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 'Get download link for EDSS documentation as ZIP file' clearly states the action (Get) and the resource (download link for ZIP), distinguishing it from siblings like get_edss_documentation which likely returns content directly.

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 such as discover_documentation_links or get_edss_documentation. The description lacks context for 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/miroslawfranek/JDSS-REST-Documentation-MCP'

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