Skip to main content
Glama

help

Get detailed command help with examples for Mnemonica Strategy's MCP, RPC, or RUN contexts to understand specific functionality.

Instructions

Get detailed help for a specific command including examples

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextYesCommand context
commandYesCommand name to get help for

Implementation Reference

  • The 'help' tool implementation is inside the CallToolRequestSchema request handler in src/server.ts, which delegates to getCommandHelp imported from command-loader.ts.
    case 'help': {
    	const { context, command } = args as {
    		context: CommandContext;
    		command: string;
    	};
    
    	if (!context || !command) {
    		return {
    			content: [{ type: 'text', text: 'Error: context and command are required' }],
    			isError: true,
    		};
    	}
    
    	const help = getCommandHelp(context, command);
    
    	if (!help) {
    		return {
    			content: [{ type: 'text', text: `No help found for command '${command}' in context '${context}'` }],
    			isError: true,
    		};
    	}
    
    	// Format help nicely
    	let text = `# ${help.name}\n\n`;
    	text += `${help.description}\n\n`;
    
    	if (help.inputSchema && help.inputSchema.properties) {
    		text += `## Parameters\n\n`;
    		const props = help.inputSchema.properties as Record<string, { type: string; description?: string; enum?: string[] }>;
    		Object.entries(props).forEach(([key, val]) => {
    			text += `- **${key}** (${val.type}${val.enum ? `, enum: [${val.enum.join(', ')}]` : ''}): ${val.description || ''}\n`;
    		});
    		text += '\n';
    	}
    
    	if (help.examples && help.examples.length > 0) {
    		text += `## Examples\n\n`;
    		help.examples.forEach((ex, i) => {
    			text += `${i + 1}. **${ex.description}**\n`;
    			text += `   \`\`\`json\n   ${JSON.stringify(ex.execute.args, null, 2)}\n   \`\`\`\n\n`;
    		});
    	}
    
    	return {
    		content: [{ type: 'text', text }],
    	};
    }
  • src/server.ts:163-180 (registration)
    The 'help' tool is registered in the ListToolsRequestSchema handler within src/server.ts.
    	name: 'help',
    	description: 'Get detailed help for a specific command including examples',
    	inputSchema: {
    		type: 'object',
    		properties: {
    			context: {
    				type: 'string',
    				enum: ['MCP', 'RPC', 'RUN'],
    				description: 'Command context',
    			},
    			command: {
    				type: 'string',
    				description: 'Command name to get help for',
    			},
    		},
    		required: ['context', 'command'],
    	},
    },
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 'gets detailed help' but doesn't clarify if this is a read-only operation, what the output format might be, or any potential side effects like rate limits or authentication needs. This leaves significant gaps for a tool with two required parameters.

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 that front-loads the core purpose ('Get detailed help for a specific command') and adds a useful detail ('including examples') without any wasted words. It's appropriately sized for a simple tool.

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 moderate complexity (two required parameters, no output schema, and no annotations), the description is minimally adequate. It explains what the tool does but lacks details on output, behavioral traits, or usage context. Without annotations or an output schema, more completeness would be beneficial, but it's not entirely inadequate.

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 schema description coverage is 100%, so the schema already documents both parameters ('context' with enum values and 'command'). The description adds minimal value beyond implying that 'command' is the target for help, but it doesn't provide additional syntax or format details. This meets the baseline for high schema coverage.

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 with a specific verb ('Get') and resource ('detailed help for a specific command'), and it includes additional context ('including examples'). However, it doesn't explicitly differentiate from sibling tools like 'execute' or 'list', which might also provide help or information, so it doesn't reach the highest score.

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 'execute' or 'list'. It lacks any mention of prerequisites, exclusions, or contextual cues, leaving the agent to infer usage based on the tool name and parameters alone.

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/mythographica/strategy'

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