Skip to main content
Glama
RSS3-Network

RSS3 MCP Server

Official
by RSS3-Network

API-getStakerProfit

Retrieve staking profit data for a staker using the RSS3 MCP Server. Query decentralized chain information through natural language to access staking performance metrics.

Instructions

Retrieve staking profit of a staker

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core execution handler for the API-getStakerProfit tool. Resolves the tool name to the corresponding OpenAPI operation using openApiLookup and invokes the remote API endpoint via the HttpClient, handling success and error responses.
    // 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:108-126 (registration)
    Dynamic registration of API-getStakerProfit (and other tools) in the tool list response. Constructs tool names as `${toolName}-${method.name}` truncated to 64 characters from the OpenAPI definitions.
    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: {},
    				},
    			});
    		}
    	}
  • Handler for retrieving the input schema of API-getStakerProfit (and other dynamic tools) via the 'API-get-input-schema' meta-tool.
    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`);
    }
  • Converts OpenAPI specifications into MCP tools structures, including the openApiLookup used to resolve tool names like API-getStakerProfit to operations.
    const mcpToolWithClients = converterWithClients.map((cwc) => {
    	const mcpTools = cwc.converter.convertToMCPTools();
    	return {
    		mcpTools,
    		client: cwc.client,
    	};
    });
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-only operation, but does not specify authentication requirements, rate limits, error conditions, or response format. For a tool with zero annotation coverage, this lack of behavioral details is a significant gap, though not contradictory, as it minimally aligns with the implied read action.

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?

The description is a single, efficient sentence: 'Retrieve staking profit of a staker.' It is front-loaded with the core action and resource, with no wasted words. However, it could be slightly more informative by specifying scope or output, but within its brevity, it effectively communicates the basic purpose without redundancy.

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 tool's complexity (implied by financial data retrieval) and the absence of annotations and output schema, the description is incomplete. It does not explain what 'staking profit' includes (e.g., time period, currency, or metrics), how results are returned, or any dependencies. For a tool likely involving data queries, more context is needed to ensure proper usage, especially without structured output documentation.

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 input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description does not add parameter details, which is appropriate since there are none to describe. This meets the baseline for tools with no parameters, as the description need not compensate for missing schema information, but it does not provide extra context like default behaviors or implicit inputs.

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 staking profit of a staker' clearly states the verb ('retrieve') and resource ('staking profit of a staker'), making the purpose understandable. However, it lacks specificity about what 'staking profit' entails (e.g., historical, current, or aggregated data) and does not differentiate from sibling tools like 'API-getStakerProfitSnapshots' or 'API-getNodeOperationProfitByAddress', which may offer similar or related data. This results in a vague but functional purpose statement.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools such as 'API-getStakerProfitSnapshots' (likely for time-series data) and 'API-getNodeOperationProfitByAddress' (node-specific profit), there is no indication of context, prerequisites, or exclusions. This absence of usage instructions leaves the agent to infer based on tool names alone, which is insufficient for optimal 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/RSS3-Network/mcp-server-rss3'

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