Skip to main content
Glama
miroslawfranek

Open-E JovianDSS REST API Documentation MCP Server

search_edss_documentation

Search EDSS documentation for specific terms, endpoints, or API operations by submitting natural language queries.

Instructions

Search for specific terms or endpoints in EDSS documentation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch term (e.g., 'patient', 'assessment', 'POST', '/api/patients')
versionNoWhich version to searchlatest

Implementation Reference

  • index.js:81-99 (registration)
    Tool registration with name, description, and input schema in the ListToolsRequestSchema handler. Declares query (required) and version (optional, default 'latest') parameters.
      name: "search_edss_documentation",
      description: "Search for specific terms or endpoints in EDSS documentation", 
      inputSchema: {
        type: "object",
        properties: {
          query: {
            type: "string",
            description: "Search term (e.g., 'patient', 'assessment', 'POST', '/api/patients')"
          },
          version: {
            type: "string",
            enum: ["latest", "trunk", "both"],
            default: "latest", 
            description: "Which version to search"
          }
        },
        required: ["query"]
      }
    },
  • Input schema defines the expected parameters for the search tool: query (required string) and version (optional string from enum ['latest', 'trunk', 'both'], default 'latest').
      name: "search_edss_documentation",
      description: "Search for specific terms or endpoints in EDSS documentation", 
      inputSchema: {
        type: "object",
        properties: {
          query: {
            type: "string",
            description: "Search term (e.g., 'patient', 'assessment', 'POST', '/api/patients')"
          },
          version: {
            type: "string",
            enum: ["latest", "trunk", "both"],
            default: "latest", 
            description: "Which version to search"
          }
        },
        required: ["query"]
      }
    },
  • Main handler for search_edss_documentation. Fetches documentation HTML from legacy URLs, uses findMatches helper to search the content, and returns results as JSON.
    async searchDocumentation(args) {
      const { query, version = "latest" } = args;
      
      try {
        const versions = version === "both" ? ["latest", "trunk"] : [version];
        const results = [];
    
        for (const ver of versions) {
          const url = ver === "latest" ? this.legacyDocUrls.latest : this.legacyDocUrls.trunk;
          const response = await fetch(url);
          
          if (response.ok) {
            const content = await response.text();
            const matches = this.findMatches(content, query, ver);
            results.push(...matches);
          }
        }
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                query: query,
                results: results,
                total: results.length
              }, null, 2)
            }
          ]
        };
      } catch (error) {
        throw new Error(`Search failed: ${error.message}`);
      }
    }
  • index.js:189-190 (registration)
    Routing registration in the CallToolRequestSchema switch-case, mapping the tool name 'search_edss_documentation' to the searchDocumentation method.
    case "search_edss_documentation":
      return await this.searchDocumentation(args);
  • Helper method used by searchDocumentation. Performs regex-based line-by-line search of the HTML content, returning matches with version, line number, content, and surrounding context.
    findMatches(content, query, version) {
      const regex = new RegExp(query, 'gi');
      const matches = [];
      const lines = content.split('\n');
    
      lines.forEach((line, index) => {
        if (regex.test(line)) {
          matches.push({
            version: version,
            line: index + 1,
            content: line.trim(),
            context: lines.slice(Math.max(0, index - 1), index + 2)
          });
        }
      });
    
      return matches;
    }
Behavior2/5

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

No annotations provided, so the description must convey behavior. It only states 'search' without detailing return format, pagination, or any side effects. Minimal behavioral insight.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single, clear sentence with no redundancy. However, it may be too brief to be fully effective. Still, it is well-structured and front-loaded.

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?

No output schema, so description should explain what the search returns. It does not mention result format, snippets, or links. Lacks context for effective use, especially given siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with inline descriptions, but the description adds no additional meaning. It does not elaborate on parameter usage or expected input formats beyond what the schema provides.

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 verb 'Search' and the resource 'EDSS documentation', indicating a search function. It distinguishes from sibling tools like 'get_edss_documentation' by focusing on term/endpoint lookup, but does not explicitly differentiate.

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 on when to use this tool versus alternatives (e.g., get_edss_documentation for full docs). No exclusion criteria or prerequisites are mentioned.

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