Skip to main content
Glama
RSS3-Network

RSS3 MCP Server

Official
by RSS3-Network

API-get_ai_intels_api_v1_ai_intel_get

Retrieve AI intelligence data from decentralized chains and social media via RSS3 API integration for natural language queries.

Instructions

Get Ai Intels

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Generic handler for all MCP tools: locates the OpenAPI operation corresponding to the tool name via openApiLookup and executes it using the HttpClient, returning the JSON response. This handles the execution of 'API-get_ai_intels_api_v1_ai_intel_get'.
    // 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) {
  • index.js:108-126 (registration)
    Dynamically registers all tools by iterating over MCP tools derived from OpenAPI specs, constructing tool names as `${toolName}-${method.name}` (truncated), which includes 'API-get_ai_intels_api_v1_ai_intel_get'.
    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: {},
    				},
    			});
    		}
    	}
  • Special tool 'API-get-input-schema' that provides the actual input schema for any registered tool, including the target, by looking up the corresponding method.inputSchema from OpenAPI.
    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 to MCP tools using OpenAPIToMCPConverter.convertToMCPTools(), creating the openApiLookup and tools used for registration and execution.
    const mcpToolWithClients = converterWithClients.map((cwc) => {
    	const mcpTools = cwc.converter.convertToMCPTools();
    	return {
    		mcpTools,
    		client: cwc.client,
    	};
    });
  • Fetches OpenAPI specifications from RSS3 endpoints (including ai.rss3.io which likely defines the /api/v1/ai-intel/get endpoint) and initializes HttpClient for execution.
    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 the full burden of behavioral disclosure. 'Get Ai Intels' only implies a read operation without detailing any behavioral traits such as authentication requirements, rate limits, response format, or potential side effects. For a tool with zero annotation coverage, this minimal description is inadequate and fails to inform the agent about how the tool behaves.

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

Conciseness2/5

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

While 'Get Ai Intels' is brief, it's under-specified rather than concise. The single phrase lacks necessary detail and structure, failing to front-load critical information about the tool's purpose or usage. Conciseness should not come at the expense of clarity, and this description sacrifices too much context for brevity.

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 the tool name (involving 'Ai Intels'), the absence of annotations, and no output schema, the description is incomplete. It doesn't explain what 'Ai Intels' are, what data is returned, or how this tool fits into the broader context of sibling tools. For a tool that likely retrieves AI-related intelligence data, more context is needed to guide effective 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 with 100% schema description coverage, meaning the input schema fully documents the absence of parameters. The description doesn't need to add parameter semantics since there are none to explain. A baseline score of 4 is appropriate as the description doesn't contradict the schema and the schema handles the parameter documentation completely.

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 'Get Ai Intels' is a tautology that essentially restates the tool name without adding meaningful clarification. It uses a generic verb 'Get' and doesn't specify what 'Ai Intels' are or what resource is being retrieved, making the purpose vague. Compared to siblings like 'getAllChips' or 'getNodeByAddress', this description fails to distinguish what makes this tool unique.

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 doesn't mention any context, prerequisites, or exclusions, and with siblings like 'getAIDataByPath' or 'getRSSActivityByPath' that might overlap with AI-related data, the lack of differentiation is a significant gap. There's no indication of what scenarios warrant selecting this specific tool.

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