Skip to main content
Glama
RSS3-Network

RSS3 MCP Server

Official
by RSS3-Network

API-batchGetAccountsActivities

Retrieve multiple accounts' activity data from decentralized chains and social platforms to analyze on-chain and off-chain interactions in a single query.

Instructions

Batch Get Accounts Activities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Generic handler for executing all dynamically generated API tools (including API-batchGetAccountsActivities). It resolves the OpenAPI operation using openApiLookup[name] and calls HttpClient.executeOperation with the parameters.
    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)
    Registers and lists all tools dynamically from OpenAPI specs, constructing names like `${toolName}-${method.name}` (e.g., API-batchGetAccountsActivities).
    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 };
    });
  • Generates MCP tools from OpenAPIToMCPConverter, creating the openApiLookup used for tool resolution and execution.
    const mcpToolWithClients = converterWithClients.map((cwc) => {
    	const mcpTools = cwc.converter.convertToMCPTools();
    	return {
    		mcpTools,
    		client: cwc.client,
    	};
    });
  • API-get-input-schema tool provides the input schema for any API tool (including API-batchGetAccountsActivities) by retrieving method.inputSchema from the OpenAPI conversion.
    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`);
    }
  • Initializes OpenAPIToMCPConverter and HttpClient from fetched RSS3 OpenAPI specs (gi.rss3.io and ai.rss3.io).
    const converterWithClients = openApiSpecs.map((o) => {
    	const converter = new OpenAPIToMCPConverter(o.spec);
    	return {
    		converter,
    		client: o.client,
    	};
    });
Behavior1/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 only states the action ('Batch Get') without explaining what 'Accounts Activities' are, whether this is a read-only operation, if it requires authentication, its rate limits, error handling, or output format. This is inadequate for a tool with zero annotation coverage, as it omits critical behavioral traits.

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?

The description is a single phrase, 'Batch Get Accounts Activities', which is concise but under-specified rather than efficiently informative. It front-loads the core action but lacks necessary elaboration, making it more of a label than a helpful description. While not verbose, it fails to provide sufficient context.

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 implied by 'Batch' and 'Accounts Activities', no annotations, and no output schema, the description is incomplete. It does not explain what the tool returns, how batching works, or any behavioral aspects. For a tool with rich sibling context and no structured support, this minimal description leaves significant gaps in understanding.

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, but since there are no parameters, this is acceptable. A baseline score of 4 is appropriate as the description doesn't need to compensate for missing parameter documentation.

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 'Batch Get Accounts Activities' is essentially a tautology that restates the tool name with minimal elaboration. It specifies the verb 'Get' and resource 'Accounts Activities' but lacks detail on what 'Accounts Activities' entails or how 'Batch' modifies the operation. While it distinguishes from some siblings like 'getAccountActivities' (singular vs. batch), it doesn't clearly differentiate from 'API-batchGetFederatedAccountsActivities' beyond the 'Federated' qualifier.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, appropriate contexts, or exclusions, nor does it reference sibling tools like 'getAccountActivities' (for single operations) or 'API-batchGetFederatedAccountsActivities' (for federated data). This leaves the agent with no basis for selecting among similar tools.

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