Skip to main content
Glama
Vanshika-Rana

Payman AI Documentation MCP Server

get-sdk-help

Get help with Node.js or Python SDK usage by specifying the feature or class you need assistance with.

Instructions

Get help with Node.js or Python SDK usage

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sdkYesWhich SDK you need help with
featureYesWhich SDK feature or class you need help with

Implementation Reference

  • Handler function that implements the logic for the 'get-sdk-help' tool. It searches relevant SDK documentation topics for the specified SDK (nodejs or python) and feature, extracts relevant sections, ranks them by relevance, and returns formatted help text with content excerpts and links to full documentation.
    	async ({ sdk, feature }) => {
    		log(`Getting help for ${sdk} SDK feature: ${feature}`);
    
    		const sdkTopics = [
    			"setup-and-installation",
    			"create-payees",
    			"send-payments",
    			"create-payee",
    			"search-payees",
    			"check-balances",
    		];
    
    		const helpPromises = sdkTopics.map(async (topic) => {
    			const content = await fetchDocMarkdown(pathMap[topic]);
    
    			const sdkIdentifier =
    				sdk === "nodejs"
    					? ["node", "nodejs", "javascript", "js"]
    					: ["python", "py"];
    
    			const relevance = sdkIdentifier.some(
    				(id) =>
    					content.toLowerCase().includes(id) &&
    					content.toLowerCase().includes(feature.toLowerCase()) &&
    					Math.abs(
    						content.toLowerCase().indexOf(id) -
    							content.toLowerCase().indexOf(feature.toLowerCase())
    					) < 500
    			);
    
    			if (!relevance) return null;
    
    			const lines = content.split("\n");
    			const featureIndex = lines.findIndex((line) =>
    				line.toLowerCase().includes(feature.toLowerCase())
    			);
    
    			if (featureIndex === -1) return null;
    
    			let headingIndex = featureIndex;
    			while (headingIndex > 0 && !lines[headingIndex].startsWith("#")) {
    				headingIndex--;
    			}
    
    			const sectionHeading = lines[headingIndex];
    			const sectionContent = lines
    				.slice(headingIndex, featureIndex + 20)
    				.join("\n");
    
    			return {
    				topic,
    				heading: sectionHeading,
    				content: sectionContent,
    				relevance:
    					(content.toLowerCase().includes(sdk) ? 2 : 1) +
    					(sectionContent
    						.toLowerCase()
    						.includes(feature.toLowerCase())
    						? 3
    						: 0),
    			};
    		});
    
    		const helpResults = (await Promise.all(helpPromises)).filter(Boolean);
    
    		helpResults.sort((a, b) => (b?.relevance || 0) - (a?.relevance || 0));
    
    		if (helpResults.length === 0) {
    			return {
    				content: [
    					{
    						type: "text",
    						text: `No specific help found for ${feature} in the ${sdk} SDK. Try checking the full SDK documentation with get-documentation or using more generic terms.`,
    					},
    				],
    			};
    		}
    
    		let helpText = `# ${sdk.toUpperCase()} SDK Help: ${feature}\n\n`;
    
    		helpResults.forEach((result) => {
    			if (!result) return;
    			helpText += `## From ${topicMetadata[result.topic].title}\n\n`;
    			helpText += `${result.content}\n\n`;
    			helpText += `*For complete documentation, use get-documentation with topic "${result.topic}"*\n\n---\n\n`;
    		});
    
    		helpText += `## Additional Resources\n\n`;
    		helpText += `- Setup and Installation: use get-documentation with topic "setup-and-installation"\n`;
    		helpText += `- Error Handling: use get-documentation with topic "error-handling"\n`;
    		helpText += `- For code examples, try the get-code-examples tool with feature="${feature}" and language="${sdk}"\n`;
    
    		return {
    			content: [
    				{
    					type: "text",
    					text: helpText,
    				},
    			],
    		};
    	}
    );
  • Input schema for the 'get-sdk-help' tool using Zod, defining parameters 'sdk' (enum: nodejs/python) and 'feature' (string).
    {
    	sdk: z
    		.enum(["nodejs", "python"])
    		.describe("Which SDK you need help with"),
    	feature: z
    		.string()
    		.describe("Which SDK feature or class you need help with"),
    },
  • src/index.ts:515-517 (registration)
    Registration of the 'get-sdk-help' tool on the MCP server using server.tool(), including name, description, schema, and inline handler.
    server.tool(
    	"get-sdk-help",
    	"Get help with Node.js or Python SDK usage",
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 the tool 'Get help' but doesn't clarify what form this help takes (e.g., documentation snippets, troubleshooting advice, API references), whether it requires authentication, rate limits, or error handling. For a tool with no annotation coverage, this is a significant gap in behavioral context.

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 a single, efficient sentence: 'Get help with Node.js or Python SDK usage'. It is front-loaded with the core purpose, has zero wasted words, and is appropriately sized for a simple tool. Every part of the sentence earns its place by specifying the action and target.

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 (2 required parameters, no output schema, no annotations), the description is incomplete. It doesn't explain what kind of help is returned (e.g., text, links, code), how results are formatted, or any behavioral traits. Without annotations or output schema, the description should provide more context to guide the agent effectively, but it falls short.

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 clear parameter descriptions in the schema itself (e.g., 'Which SDK you need help with' for 'sdk'). The description adds no additional parameter semantics beyond what the schema provides, such as examples or usage tips. With high schema coverage, the baseline score of 3 is appropriate as the schema handles the heavy lifting.

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 as 'Get help with Node.js or Python SDK usage', which is a specific verb ('Get help') with resources ('Node.js or Python SDK usage'). However, it doesn't explicitly differentiate from sibling tools like 'get-code-examples' or 'get-documentation', which might provide overlapping functionality. The purpose is clear but lacks sibling distinction.

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 like 'get-code-examples' or 'search-documentation'. It implies usage for SDK help but doesn't specify contexts, prerequisites, or exclusions. This leaves the agent without clear direction on tool selection among similar siblings.

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/Vanshika-Rana/payman-mcp-server'

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