Skip to main content
Glama

list_legends

Access a curated list of legendary founders and investors available for chat, filterable by category or with a fun vibe. Includes tech titans, investors, startup sages, and crypto builders.

Instructions

List all legendary founders and investors you can chat with.

The council includes:

  • Tech Titans: Elon Musk, Steve Jobs, Jeff Bezos, Jensen Huang

  • Investors: Warren Buffett, Charlie Munger, Peter Thiel, Marc Andreessen

  • Startup Sages: Paul Graham, Sam Altman, Naval Ravikant, Reid Hoffman

  • Crypto Builders: CZ, Anatoly Yakovenko, Mert Mumtaz, Michael Heinrich

Each legend has unique thinking frameworks, principles, and perspectives.

Set vibe="fun" for a more entertaining presentation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by category (e.g., "crypto", "investor", "founder", "tech")
vibeNoOutput style: "serious" (default) or "fun" for meme mode

Implementation Reference

  • Main handler function that lists all legends, optionally filtered by category. Calls getLegendSummaries() from the loader.
    export function listLegends(input?: ListLegendsInput): ListLegendsResult {
      let legends = getLegendSummaries();
    
      // Filter by category if provided
      if (input?.category) {
        const cat = input.category.toLowerCase();
        legends = legends.filter(l =>
          l.tags.some(t => t.toLowerCase().includes(cat)) ||
          l.expertise.some(e => e.toLowerCase().includes(cat))
        );
      }
    
      return {
        count: legends.length,
        legends,
      };
    }
  • Input and output type definitions for the list_legends tool.
    export interface ListLegendsInput {
      category?: string;
      vibe?: 'serious' | 'fun';
    }
  • MCP tool definition object with name 'list_legends', description, and inputSchema for registration.
    // MCP Tool Definition
    export const listLegendsTool = {
      name: 'list_legends',
      description: `List all legendary founders and investors you can chat with.
    
    The council includes:
    - **Tech Titans**: Elon Musk, Steve Jobs, Jeff Bezos, Jensen Huang
    - **Investors**: Warren Buffett, Charlie Munger, Peter Thiel, Marc Andreessen
    - **Startup Sages**: Paul Graham, Sam Altman, Naval Ravikant, Reid Hoffman
    - **Crypto Builders**: CZ, Anatoly Yakovenko, Mert Mumtaz, Michael Heinrich
    
    Each legend has unique thinking frameworks, principles, and perspectives.
    
    Set vibe="fun" for a more entertaining presentation.`,
      inputSchema: {
        type: 'object' as const,
        properties: {
          category: {
            type: 'string',
            description: 'Filter by category (e.g., "crypto", "investor", "founder", "tech")',
          },
          vibe: {
            type: 'string',
            enum: ['serious', 'fun'],
            description: 'Output style: "serious" (default) or "fun" for meme mode',
          },
        },
        required: [] as string[],
      },
    };
  • src/index.ts:56-60 (registration)
    The listLegendsTool is included in the allTools array (src/tools/index.ts:22-31) which is returned when the server handles ListToolsRequestSchema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: allTools,
      };
    });
  • Formats the legend list as markdown for display, supporting 'serious' and 'fun' vibes.
    export function formatLegendsMarkdown(result: ListLegendsResult, vibe: 'serious' | 'fun' = 'serious'): string {
      const lines: string[] = [];
    
      if (vibe === 'fun') {
        lines.push(`# 🎭 The Council of Legends (${result.count})`);
        lines.push('');
        lines.push('*Your personal board of advisors. They\'ve built trillion-dollar companies, lost billions, and lived to tell the tale.*');
        lines.push('');
        lines.push('---');
        lines.push('');
    
        for (const legend of result.legends) {
          const emoji = LEGEND_VIBES[legend.id] || '💡';
          lines.push(`### ${legend.name}`);
          lines.push(`**ID:** \`${legend.id}\` ${emoji}`);
          lines.push('');
        }
    
        lines.push('---');
        lines.push('');
        lines.push('*"The best time to get advice from a legend was 20 years ago. The second best time is now."*');
        lines.push('');
        lines.push('Use `summon_legend` to start a conversation.');
      } else {
        lines.push(`# Available Legends (${result.count})`);
        lines.push('');
        lines.push('Chat with legendary founders and investors. Each brings unique frameworks and perspectives.');
        lines.push('');
    
        for (const legend of result.legends) {
          lines.push(`## ${legend.name}`);
          lines.push(`**ID:** \`${legend.id}\``);
          lines.push(`*${legend.description}*`);
          if (legend.expertise.length > 0) {
            lines.push(`**Expertise:** ${legend.expertise.join(', ')}`);
          }
          if (legend.tags.length > 0) {
            lines.push(`**Tags:** ${legend.tags.join(', ')}`);
          }
          lines.push('');
        }
    
        lines.push('---');
        lines.push('');
        lines.push('**Disclaimer:** These are AI personas for educational purposes. Not affiliated with real individuals.');
        lines.push('');
        lines.push('Use `summon_legend` with a legend ID to start a conversation.');
      }
    
      return lines.join('\n');
    }
Behavior3/5

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

Given no annotations, the description carries full burden. It states the tool lists all legends and mentions the vibe effect. But it does not disclose if it's read-only, any side effects, or authentication needs. Moderate transparency for a listing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a bulleted list and front-loaded main purpose. It is slightly verbose but each sentence adds context about the tool's offerings.

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

Completeness4/5

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

For a simple list tool with two optional parameters and no output schema, the description covers the main purpose, categories, and vibe option. It lacks details on pagination or errors but is sufficient for basic use.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the vibe parameter effect ('more entertaining presentation') and listing categories, but the schema already defines enum and descriptions.

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

Purpose5/5

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

The description clearly states the tool lists all legendary founders and investors, with specific categories enumerated. It is a specific verb+resource that distinguishes it from siblings like search_legends or get_legend_context.

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

Usage Guidelines4/5

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

The description explains what the tool does and mentions the vibe parameter for presentation style. However, it does not explicitly advise when to use this tool over alternatives like search_legends for filtering or get_legend_context for details.

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/AytuncYildizli/legends-mcp'

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