Skip to main content
Glama

get_themes

List available themes for your account to obtain valid theme IDs before creating a presentation.

Instructions

List themes available to the authenticated account. Call this before generate_presentation when you need valid theme_id values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.js:184-198 (registration)
    Registration of the 'get_themes' tool via server.registerTool with name 'get_themes', description about listing themes, and an empty input schema.
    server.registerTool(
      "get_themes",
      {
        description:
          "List themes available to the authenticated account. Call this before generate_presentation when you need valid theme_id values.",
        inputSchema: {},
      },
      async () => {
        try {
          return await callRemoteTool("get_themes", {});
        } catch (error) {
          return normalizeError(error);
        }
      },
    );
  • Handler function for 'get_themes' - calls the remote Alai MCP endpoint with the tool name 'get_themes' and empty arguments, delegating execution to the upstream service.
    async () => {
      try {
        return await callRemoteTool("get_themes", {});
      } catch (error) {
        return normalizeError(error);
      }
    },
  • The callRemoteTool helper function that connects to the remote Alai MCP endpoint via StreamableHTTPClientTransport, calls the specified tool, and returns the result. This is the underlying mechanism used by the get_themes handler.
    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(() => {});
      }
    }
  • The theme_id input schema in basePresentationInput that references theme identifiers from get_themes, showing how the output of get_themes is consumed downstream.
    theme_id: z
      .string()
      .optional()
      .describe("Theme identifier from get_themes. Use this to control layout family."),
Behavior3/5

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

With no annotations, the description carries full behavioral burden. It indicates a read operation with no side effects, but lacks details on authentication, rate limits, or response structure. Adequate but minimal.

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 sentences, both front-loaded: first defines purpose, second gives usage tip. No wasted words, excellent conciseness.

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?

Given no parameters and no output schema, the description is mostly complete, explaining what it does and why to use it. It could mention the output format, but the tip implies theme_id values are returned. Slightly lacking, but overall adequate.

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, so the schema is fully covered. The description adds no extra parameter info, but none is needed. Baseline score for zero parameters is 4.

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 themes and specifies it's for the authenticated account. It also provides a usage tip linking to generate_presentation, distinguishing it from other list tools like get_vibes.

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 explicitly advises to call this before generate_presentation to obtain valid theme_id values, giving clear context for when to use it. It does not mention exclusions or alternatives, but the guidance is sufficient for this simple tool.

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