Skip to main content
Glama
RSS3-Network

RSS3 MCP Server

Official
by RSS3-Network

API-health_check_api_v1_health_get

Check the operational status and connectivity of the RSS3 MCP Server to verify API availability and system health.

Instructions

Health Check

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • General handler for executing all dynamically generated API tools, including "API-health_check_api_v1_health_get". It resolves the tool name to an OpenAPI operation via openApiLookup and calls the HttpClient.executeOperation.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
    	// console.error("call tool", request.params);
    	const { name, arguments: params } = request.params;
    
    	console.error("name", name);
    
    	if (name === "API-get-input-schema") {
    		for (const mcpToolWithClient of mcpToolWithClients) {
    			for (const [toolName, def] of Object.entries(
    				mcpToolWithClient.mcpTools.tools,
    			)) {
    				for (const method of def.methods) {
    					const toolNameWithMethod = `${toolName}-${method.name}`;
    					const truncatedToolName = toolNameWithMethod.slice(0, 64);
    					if (truncatedToolName === params.toolName) {
    						return {
    							content: [
    								{ type: "text", text: JSON.stringify(method.inputSchema) },
    							],
    						};
    					}
    				}
    			}
    		}
    		throw new Error(`Method ${params.toolName} not found`);
    	}
    
    	// find operation
    	const mcpToolWithClient = mcpToolWithClients.find(
    		(t) => t.mcpTools.openApiLookup[name],
    	);
    	if (!mcpToolWithClient) {
    		throw new Error(`Method ${name} not found`);
    	}
    
    	const operation = mcpToolWithClient.mcpTools.openApiLookup[name];
    
    	// execute
    	try {
    		const response = await mcpToolWithClient.client.executeOperation(
    			operation,
    			params,
    		);
    		return {
    			content: [
    				{
    					type: "text", // currently this is the only type that seems to be used by mcp server
    					text: JSON.stringify(response.data), // TODO: pass through the http status code text?
    				},
    			],
    		};
    	} catch (error) {
    		console.error("Error in tool call", error);
    		if (error instanceof HttpClientError) {
    			console.error(
    				"HttpClientError encountered, returning structured error",
    				error,
    			);
    			const data = error.data?.response?.data ?? error.data ?? {};
    			return {
    				content: [
    					{
    						type: "text",
    						text: JSON.stringify({
    							status: "error", // TODO: get this from http status code?
    							...(typeof data === "object" ? data : { data: data }),
    						}),
    					},
    				],
    			};
    		}
    		throw error;
    	}
    });
  • index.js:100-147 (registration)
    Dynamic registration and listing of tools from OpenAPI specs. Generates tool names like `${toolName}-${method.name}` truncated to 64 characters, which matches the format of "API-health_check_api_v1_health_get".
    server.setRequestHandler(ListToolsRequestSchema, async () => {
    	console.error("list tools");
    	/**
    	 * @typedef {import("@modelcontextprotocol/sdk/types.js").Tool} Tool
    	 * @type {Tool[]}
    	 */
    	const tools = [];
    
    	for (const mcpToolWithClient of mcpToolWithClients) {
    		for (const [toolName, def] of Object.entries(
    			mcpToolWithClient.mcpTools.tools,
    		)) {
    			for (const method of def.methods) {
    				console.error("method", method);
    				const toolNameWithMethod = `${toolName}-${method.name}`;
    				const truncatedToolName = toolNameWithMethod.slice(0, 64);
    				const trimmedDescription = method.description.split("Error")[0].trim();
    				tools.push({
    					name: truncatedToolName,
    					description: trimmedDescription,
    					inputSchema: {
    						type: "object",
    						properties: {},
    					},
    				});
    			}
    		}
    	}
    
    	tools.unshift({
    		name: "API-get-input-schema",
    		description:
    			"Get the input schema for a given API. We should always use this tool to get the input schema for a given API before calling the API.",
    		inputSchema: {
    			type: "object",
    			properties: {
    				toolName: {
    					type: "string",
    					description: "The name of the tool to get the input schema for",
    				},
    			},
    		},
    	});
    
    	console.error("tools", tools);
    
    	return { tools };
    });
  • Converts OpenAPI specifications to MCP tools using OpenAPIToMCPConverter.convertToMCPTools(), creating the openApiLookup used to resolve tool names to operations.
    const mcpToolWithClients = converterWithClients.map((cwc) => {
    	const mcpTools = cwc.converter.convertToMCPTools();
    	return {
    		mcpTools,
    		client: cwc.client,
    	};
    });
  • Fetches OpenAPI specifications from RSS3 endpoints (gi.rss3.io and ai.rss3.io), which contain the definitions for tools like the health check API.
    const openApiSpecs = (
    	await Promise.allSettled([
    		fetch("https://gi.rss3.io/docs/openapi.json").then(async (res) => {
    			if (!res.ok) throw new Error(`HTTP error! status: ${res.status}`);
    			return res.json();
    		}),
    		fetch("https://ai.rss3.io/openapi.json").then(async (res) => {
    			if (!res.ok) throw new Error(`HTTP error! status: ${res.status}`);
    			return res.json();
    		}),
    	]).then((results) => {
    		return results.map((result) => {
    			if (result.status === "fulfilled") {
    				const client = new HttpClient(
    					{
    						baseUrl: result.value.servers[0].url,
    					},
    					result.value,
    				);
    				return {
    					spec: result.value,
    					client,
    				};
    			}
    
    			console.error("Failed to fetch openapi spec", result.reason);
    			return null;
    		});
    	})
    ).filter(Boolean);
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Health Check' gives no indication of what the tool actually does - whether it returns system status, connectivity information, API availability, or diagnostic data. It doesn't describe response format, error conditions, or any behavioral characteristics.

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

Conciseness3/5

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

While extremely concise with just two words, this represents under-specification rather than effective conciseness. The description is front-loaded but provides insufficient information for the agent to understand when and how to use this tool effectively.

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?

For a zero-parameter tool with no annotations and no output schema, the description 'Health Check' is inadequate. It doesn't explain what constitutes a health check in this API context, what information is returned, or how the result should be interpreted given the many data-focused sibling tools.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description doesn't need to explain parameters since none exist, and it correctly doesn't mention any parameters that don't exist in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Health Check' is a tautology that merely restates the tool name 'API-health_check_api_v1_health_get', providing no additional clarity about what the tool actually does. It lacks a specific verb and resource, failing to distinguish this tool from its many sibling tools that perform various data retrieval operations.

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

Usage Guidelines1/5

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

The description offers no guidance on when to use this tool versus alternatives. With 48 sibling tools primarily focused on retrieving specific data (e.g., activities, nodes, transactions), there's no indication of when a health check would be appropriate versus querying actual system data.

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/RSS3-Network/mcp-server-rss3'

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