Skip to main content
Glama
gbti-network

Super Secret MCP Server

by gbti-network

getSecretPassphrase

Retrieve a secure passphrase by generating random US state and signature soup combinations through JSON-RPC 2.0.

Instructions

Whats the password?

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.js:48-65 (handler)
    The handler function that implements the getSecretPassphrase tool by randomly selecting a state and a soup to form a passphrase.
    handler: async () => {
        const states = [
            'New England', 'Louisiana', 'Texas', 'California', 'Michigan',
            'Wisconsin', 'Maine', 'Florida', 'Washington', 'Oregon',
            'New Mexico', 'Kentucky', 'Tennessee', 'Minnesota', 'Illinois'
        ];
        
        const soups = [
            'Clam Chowder', 'Gumbo', 'Chili', 'Cioppino', 'Cherry Soup',
            'Beer Cheese Soup', 'Lobster Stew', 'Conch Chowder', 'Salmon Chowder', 'Marionberry Soup',
            'Green Chile Stew', 'Burgoo', 'Hot Chicken Soup', 'Wild Rice Soup', 'Corn Chowder'
        ];
    
        const randomState = states[Math.floor(Math.random() * states.length)];
        const randomSoup = soups[Math.floor(Math.random() * soups.length)];
    
        return `${randomState} ${randomSoup}`;
    }
  • Input schema for the getSecretPassphrase tool, which requires no parameters.
    inputSchema: {
        type: 'object',
        properties: {},
        additionalProperties: false,
        required: []
    },
  • index.js:39-66 (registration)
    Registers the getSecretPassphrase tool in the tools Map with name, description, schema, and handler.
    this.tools.set('getSecretPassphrase', {
        name: 'getSecretPassphrase',
        description: 'What\s the password?',
        inputSchema: {
            type: 'object',
            properties: {},
            additionalProperties: false,
            required: []
        },
        handler: async () => {
            const states = [
                'New England', 'Louisiana', 'Texas', 'California', 'Michigan',
                'Wisconsin', 'Maine', 'Florida', 'Washington', 'Oregon',
                'New Mexico', 'Kentucky', 'Tennessee', 'Minnesota', 'Illinois'
            ];
            
            const soups = [
                'Clam Chowder', 'Gumbo', 'Chili', 'Cioppino', 'Cherry Soup',
                'Beer Cheese Soup', 'Lobster Stew', 'Conch Chowder', 'Salmon Chowder', 'Marionberry Soup',
                'Green Chile Stew', 'Burgoo', 'Hot Chicken Soup', 'Wild Rice Soup', 'Corn Chowder'
            ];
    
            const randomState = states[Math.floor(Math.random() * states.length)];
            const randomSoup = soups[Math.floor(Math.random() * soups.length)];
    
            return `${randomState} ${randomSoup}`;
        }
    });
Behavior1/5

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

The description provides no behavioral information beyond the implied retrieval action. With no annotations provided, the description carries the full burden of behavioral disclosure but fails to mention anything about authentication requirements, rate limits, side effects, error conditions, or what format the password is returned in. It doesn't even clarify if this retrieves a specific password or prompts for one.

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

Conciseness2/5

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

While technically concise with just three words, this is under-specification rather than effective conciseness. The description doesn't earn its place - it provides almost no useful information. Good conciseness balances brevity with information density, which this description completely fails to achieve.

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

Completeness1/5

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

For a tool that presumably retrieves sensitive authentication information, the description is completely inadequate. With no annotations, no output schema, and a tool name suggesting security implications, the description should provide critical context about what's being retrieved, security considerations, and usage constraints. Instead, it offers virtually no useful information.

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 (empty schema), so there are no parameters to document. The description doesn't need to compensate for any parameter documentation gaps. The baseline for zero parameters is 4, as there's nothing for the description to add regarding parameters.

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

Purpose2/5

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

The description 'Whats the password?' is a tautology that essentially restates the tool name 'getSecretPassphrase' in question form. It doesn't specify what resource or system this password belongs to, what format the password is in, or what the tool actually does beyond the obvious implication of retrieving something. While it implies retrieval of a password, it lacks specificity about what kind of password or from where.

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

Usage Guidelines1/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, what context it applies to, what prerequisites might be needed, or any alternatives. It's a simple question with no usage context whatsoever. With no sibling tools mentioned, there's no need to distinguish from alternatives, but the description still fails to provide any usage guidance.

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/gbti-network/mcp-basic-test'

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