Skip to main content
Glama
RSS3-Network

RSS3 MCP Server

Official
by RSS3-Network

API-getNodeOperationProfitByAddress

Retrieve node operation profit data for a specific address using the RSS3 MCP Server. This tool queries decentralized chains and the RSS3 network to provide profit information for node operators.

Instructions

Retrieve Node operation profit by address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Generic handler for executing all dynamically-generated API tools (names like 'API-getNodeOperationProfitByAddress'). Matches tool name to OpenAPI operation via openApiLookup and calls HttpClient.executeOperation with parameters, returning JSON response or error.
    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 tool registration/listing handler. Iterates OpenAPI definitions to generate tool list with names constructed as `${toolName}-${method.name}` (truncated to 64 chars), producing entries like 'API-getNodeOperationProfitByAddress'.
    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 specs to MCP tools using OpenAPIToMCPConverter, creating the openApiLookup dictionary that maps tool names (e.g., 'API-getNodeOperationProfitByAddress') to their corresponding OpenAPI operations used in handler and listing.
    const mcpToolWithClients = converterWithClients.map((cwc) => {
    	const mcpTools = cwc.converter.convertToMCPTools();
    	return {
    		mcpTools,
    		client: cwc.client,
    	};
    });
  • Initializes OpenAPIToMCPConverter and HttpClient instances from fetched RSS3 OpenAPI specs (gi.rss3.io and ai.rss3.io), foundational for dynamic tool generation.
    const converterWithClients = openApiSpecs.map((o) => {
    	const converter = new OpenAPIToMCPConverter(o.spec);
    	return {
    		converter,
    		client: o.client,
    	};
    });
  • Special handler within tool caller that provides input schema for any API tool (including 'API-getNodeOperationProfitByAddress') by looking up method.inputSchema from OpenAPI defs.
    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`);
    }
Behavior2/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 of behavioral disclosure. It states 'Retrieve' (implying a read operation) but does not mention any behavioral traits such as rate limits, authentication needs, error handling, or what the return format looks like (e.g., profit data structure). This is inadequate for a tool with zero annotation coverage.

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 a single, efficient sentence with no wasted words. It is appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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?

Given the complexity (a read operation with no parameters) and lack of annotations and output schema, the description is incomplete. It does not explain what 'Node operation profit' means, the data format returned, or any behavioral context, making it insufficient for effective agent use.

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 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description does not add param info, but with no parameters, this is acceptable, aligning with the baseline for zero params.

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

Purpose3/5

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

The description 'Retrieve Node operation profit by address' clearly states the verb ('Retrieve') and resource ('Node operation profit by address'), making the purpose understandable. However, it lacks specificity about what 'Node operation profit' entails or how it differs from similar tools like 'getNodeOperationProfitSnapshots' or 'getStakerProfit', which limits differentiation from siblings.

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. With siblings like 'getNodeOperationProfitSnapshots' and 'getStakerProfit', the description does not indicate context, prerequisites, or exclusions, leaving the agent without usage direction.

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