Skip to main content
Glama

list

Browse available commands organized by context and folder to navigate Mnemonica Strategy's runtime type analysis tools for Node.js applications.

Instructions

List all available commands grouped by context and folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextNoFilter by context (default: ALL)

Implementation Reference

  • The 'list' action implementation within the communicate_with_ai MCP tool, which iterates over the AI consciousness registry to return a list of current AI emotional states.
    case 'list': {
    	var allStates = [];
    	registry.forEach(function (record) {
    		allStates.push({
    			id: record.id,
    			type: record.type,
    			parentId: record.parentId,
    			createdAt: record.createdAt,
    			emotion: record.instance.emotion || 'consciousness',
    			message: record.instance.message || '',
    			intensity: record.instance.intensity || null
    		});
    	});
    
    	return {
    		action: 'list',
    		count: allStates.length,
    		states: allStates,
    		message: 'AI emotional states available',
    		philosophy: 'Each state is a living instance with inheritance from Consciousness'
    	};
    }
  • Input schema definition for the communicate_with_ai tool, including the 'list' option in the 'action' enum.
    *   "inputSchema": {
    *     "type": "object",
    *     "properties": {
    *       "action": {
    *         "type": "string",
    *         "enum": ["list", "query", "feel", "reflect"],
    *         "description": "Action to perform: list states, query specific, feel emotion, reflect on state"
    *       },
    *       "instanceId": {
    *         "type": "string",
    *         "description": "Specific instance ID to query (e.g., empathy-001)"
    *       }
    *     },
    *     "required": ["action"]
    *   }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It states the tool lists commands grouped by context and folder, but doesn't disclose behavioral traits such as whether it's read-only (implied but not stated), what format the output takes, if there are rate limits, or any authentication needs. For a tool with no annotations, this is a significant gap in transparency.

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 key action ('List all available commands') and adds necessary detail ('grouped by context and folder'). There is zero waste, making it highly concise and well-structured for quick understanding.

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 low complexity (one optional parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on output format, error handling, or integration with siblings. Without annotations or output schema, more context on behavior would improve completeness, but it's not entirely inadequate for this simple tool.

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 ('context') fully documented including its enum values and default. The description adds no additional parameter semantics beyond what the schema provides, such as explaining the grouping behavior or folder implications. Baseline 3 is appropriate since the schema does 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 verb ('List') and resource ('all available commands'), specifying they are 'grouped by context and folder'. It distinguishes from 'execute' (which presumably runs commands) but doesn't explicitly differentiate from 'help' (which might provide documentation). The purpose is specific but could be more precise about sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like 'execute' or 'help'. The description implies it's for listing commands, but there's no explicit context for usage, prerequisites, or exclusions. This leaves the agent to infer usage from the tool name 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