Skip to main content
Glama
alxspiker

AI Meta MCP Server

list_functions

Discover available custom MCP functions to understand what tools AI models can create and execute within the meta-function architecture.

Instructions

List all custom MCP functions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_functions' tool. It logs the action, maps over customTools to create a list of function metadata (name, description, executionEnvironment, dates), and returns it as a JSON string in the MCP response format.
    async () => {
      console.error(`Listing all functions`);
      
      const functionList = Object.entries(customTools).map(([name, tool]) => ({
        name,
        description: tool.description,
        executionEnvironment: tool.executionEnvironment,
        createdAt: tool.createdAt,
        updatedAt: tool.updatedAt,
      }));
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(functionList, null, 2),
          },
        ],
      };
    }
  • src/index.ts:460-484 (registration)
    The registration of the 'list_functions' tool using server.tool(), including name, description, empty input schema (no parameters), and the handler function.
    server.tool(
      "list_functions",
      "List all custom MCP functions",
      {},
      async () => {
        console.error(`Listing all functions`);
        
        const functionList = Object.entries(customTools).map(([name, tool]) => ({
          name,
          description: tool.description,
          executionEnvironment: tool.executionEnvironment,
          createdAt: tool.createdAt,
          updatedAt: tool.updatedAt,
        }));
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(functionList, null, 2),
            },
          ],
        };
      }
    );
  • The input schema for 'list_functions' tool, which is empty object indicating no input parameters required.
    {},
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't mention whether this is a read-only operation, what format the list returns (e.g., paginated, sorted), or any limitations (e.g., rate limits, authentication needs).

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, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it immediately understandable without unnecessary elaboration.

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?

For a zero-parameter list tool with no output schema, the description is minimally adequate but lacks completeness. It doesn't explain return values, behavioral traits, or usage context, leaving gaps that could hinder an agent's understanding despite the simple input schema.

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, so no parameter documentation is needed. The description doesn't add parameter details, but that's appropriate here, meeting the baseline for zero-parameter tools.

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 custom MCP functions'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'get_function_details' which might retrieve a single function, but the scope 'all' provides some implicit 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?

No guidance is provided on when to use this tool versus alternatives like 'get_function_details' for single functions or 'define_function' for creating new ones. The description lacks context about prerequisites, timing, or comparison with sibling tools.

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/alxspiker/ai-meta-mcp-server'

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