Skip to main content
Glama
RSS3-Network

RSS3 MCP Server

Official
by RSS3-Network

API-getNodeByAddress

Retrieve RSS3 network node data by address to query decentralized chain and social media information through the RSS3 API.

Instructions

Retrieve Node by address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for executing the API-getNodeByAddress tool: finds the corresponding OpenAPI operation via openApiLookup[name] and calls HttpClient.executeOperation, returning the JSON response or structured error.
    // 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:107-126 (registration)
    Dynamic registration of tools in ListTools response: constructs tool names like 'API-getNodeByAddress' from OpenAPI toolName-method.name pairs.
    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: {},
    				},
    			});
    		}
    	}
  • Schema retrieval helper: provides the input schema for 'API-getNodeByAddress' and other tools by looking up the matching method.inputSchema.
    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 specs to MCP tools dictionary and lookup, populating tools and openApiLookup used for 'API-getNodeByAddress'.
    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' which implies a read operation, but doesn't cover authentication needs, rate limits, error handling, or response format. For a tool with zero annotation coverage, this is a significant gap in transparency about how it behaves.

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 extremely concise ('Retrieve Node by address') with zero wasted words. It's front-loaded with the core action and resource, making it efficient for quick understanding, though it lacks depth.

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 no annotations, no output schema, and a simple tool with 0 parameters, the description is incomplete. It doesn't explain what 'Node' means in this context, what data is returned, or any behavioral aspects like authentication or errors. For a retrieval tool, more context is needed to be fully useful to an agent.

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, so no parameters need documentation. The description doesn't add parameter details, but that's appropriate since there are none. A baseline of 4 is applied as the description doesn't need to compensate for any parameter gaps.

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 by address' clearly states the verb ('Retrieve') and resource ('Node'), but it's vague about what 'Node' represents in this context and doesn't differentiate from sibling tools like API-getAllNodes or API-getNodeAssets. It provides basic purpose but lacks specificity about the domain or what distinguishes this retrieval from others.

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 like API-getAllNodes (for listing all nodes) or API-getNodeAssets (for node assets). The description doesn't mention prerequisites, context, or exclusions, leaving the agent with no usage direction beyond the basic purpose.

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