Skip to main content
Glama
RSS3-Network

RSS3 MCP Server

Official
by RSS3-Network

API-get-input-schema

Retrieve the required input structure for any RSS3 API tool to ensure proper data formatting before making API calls.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolNameNoThe name of the tool to get the input schema for

Implementation Reference

  • Handler function for the 'API-get-input-schema' tool. It iterates through the MCP tools derived from OpenAPI specs, matches the provided toolName (truncated), and returns the inputSchema of the matching method as JSON text content.
    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`);
    }
  • index.js:129-142 (registration)
    Registers the 'API-get-input-schema' tool in the listTools response by unshifting it to the tools array, providing its name, description, and inputSchema.
    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",
    			},
    		},
    	},
    });
  • Input schema definition for the 'API-get-input-schema' tool, specifying a 'toolName' string property.
    inputSchema: {
    	type: "object",
    	properties: {
    		toolName: {
    			type: "string",
    			description: "The name of the tool to get the input schema for",
    		},
    	},
    },
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 mentions the tool's purpose but lacks details on behavioral traits such as whether it's read-only, if it requires authentication, rate limits, error handling, or what the output format looks like (e.g., JSON schema). This leaves significant gaps in understanding how the tool behaves in practice.

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 concise and front-loaded, consisting of two sentences that directly state the tool's purpose and usage guidelines. There is no wasted language, and every sentence earns its place by providing essential information efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (simple read operation with one parameter) and the lack of annotations or output schema, the description is partially complete. It covers purpose and usage well but lacks behavioral details and output information. For a tool that fetches schemas, more context on the return format would be helpful, but the description is adequate for basic understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with one parameter ('toolName') clearly documented in the schema. The description does not add any additional meaning beyond this, as it only references 'a given API' without elaborating on parameter usage or constraints. With high schema coverage, a baseline score of 3 is appropriate, as the schema adequately handles parameter semantics.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Get the input schema for a given API.' It specifies the verb ('get') and resource ('input schema'), making it easy to understand what the tool does. However, it does not explicitly differentiate this tool from its siblings, which are all API-related but perform different operations (e.g., fetching activities, nodes, or health checks).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool: 'We should always use this tool to get the input schema for a given API before calling the API.' This clearly indicates a prerequisite step for using other API tools, offering strong contextual direction without alternatives or exclusions needed.

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