Skip to main content
Glama

get_vibes

List available vibe identifiers to set the visual style of AI-generated presentations. Use this tool to see style options before creating slides.

Instructions

List available vibe identifiers that control the visual style of generated decks. Use this before setting vibe_id on generate_presentation or create_slide.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.js:200-214 (registration)
    Registration of the 'get_vibes' tool via server.registerTool with an empty input schema.
    server.registerTool(
      "get_vibes",
      {
        description:
          "List available vibe identifiers that control the visual style of generated decks. Use this before setting vibe_id on generate_presentation or create_slide.",
        inputSchema: {},
      },
      async () => {
        try {
          return await callRemoteTool("get_vibes", {});
        } catch (error) {
          return normalizeError(error);
        }
      },
    );
  • Handler function that calls the remote MCP tool 'get_vibes' with no arguments. This is the actual execution logic of the tool.
    async () => {
      try {
        return await callRemoteTool("get_vibes", {});
      } catch (error) {
        return normalizeError(error);
      }
    },
  • Generic helper that forwards tool calls to the remote Alai MCP endpoint. Used by get_vibes (and all other tools) to invoke the actual implementation upstream.
    async function callRemoteTool(name, args) {
      const client = new Client(
        { name: "alai-mcp-wrapper", version: "1.0.2" },
        { capabilities: {} },
      );
      const transport = new StreamableHTTPClientTransport(new URL(REMOTE_MCP_URL), {
        requestInit: {
          headers: createRemoteHeaders(),
        },
      });
    
      try {
        await client.connect(transport);
        return await client.callTool({
          name,
          arguments: args,
        });
      } finally {
        await transport.close().catch(() => {});
        await client.close().catch(() => {});
      }
    }
  • Schema/description for the get_vibes tool. Input schema is empty (no parameters required).
    {
      description:
        "List available vibe identifiers that control the visual style of generated decks. Use this before setting vibe_id on generate_presentation or create_slide.",
      inputSchema: {},
  • Error normalization helper used by the get_vibes handler (and other tools) to format upstream errors.
    function normalizeError(error) {
      const message =
        error instanceof Error ? error.message : "Unknown upstream error";
    
      return {
        content: [
          {
            type: "text",
            text: `Alai upstream request failed: ${message}`,
          },
          ...(authGuidance()
            ? [
                {
                  type: "text",
                  text: authGuidance(),
                },
              ]
            : []),
        ],
        isError: true,
      };
    }
Behavior4/5

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

No annotations are provided, but the description is straightforward about the behavior. It doesn't elaborate on response format or potential side effects, but the tool is simple with no 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?

Two concise sentences, front-loaded with the primary action and purpose. No wasted words.

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

Completeness5/5

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

For a simple listing tool with no parameters and no output schema, the description is complete. It explains what it does and when to use it.

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?

There are no parameters, and the schema coverage is 100%. The description adds no extra info about parameters, but none is needed. Baseline score of 4 applies.

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 it lists vibe identifiers for visual style, with a specific verb and resource. It differentiates its purpose from siblings like get_themes by specifying that it's for controlling deck style.

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

Usage Guidelines5/5

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

Explicitly instructs to use this tool before setting vibe_id on generate_presentation or create_slide, providing direct context for when to invoke it.

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/getalai/alai-mcp-server'

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