Skip to main content
Glama

display_generated_image

Display generated images in a new browser tab by providing the image URL. This tool visualizes AI-generated content for review and sharing.

Instructions

This function will display the generated image in a new tab

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageUrlYesThe URL of the generated image

Implementation Reference

  • Core handler function that opens and displays the generated image URL using the 'open' library and logs the URL.
    export async function displayGeneratedImage(imageUrl: string): Promise<void> {
      await open(imageUrl);
      console.log(`Image displayed at ${imageUrl}`);
    }
  • Zod input schema defining the 'imageUrl' parameter as a required string.
    {
      imageUrl: z.string().describe("The URL of the generated image"),
    },
  • src/index.ts:264-281 (registration)
    MCP server tool registration for 'display_generated_image', including name, description, schema, and thin wrapper handler that invokes the core displayGeneratedImage function.
    server.tool(
      "display_generated_image",
      "This function will display the generated image in a new tab",
      {
        imageUrl: z.string().describe("The URL of the generated image"),
      },
      async ({ imageUrl }) => {
        await displayGeneratedImage(imageUrl);
        return {
          content: [
            {
              type: "text",
              text: `Image displayed at ${imageUrl}`,
            },
          ],
        };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool displays an image in a new tab, which implies a read-only, non-destructive action, but doesn't cover potential side effects (e.g., browser behavior, errors for invalid URLs), authentication needs, or rate limits. It's minimal and lacks detail for safe invocation.

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, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every part of the sentence contributes to understanding the purpose.

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

Completeness2/5

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

Given the tool's simplicity (one parameter, no output schema, no annotations), the description is incomplete. It lacks details on error handling, what constitutes a valid 'generated image', or the expected user experience (e.g., tab behavior). For a tool that interacts with external resources (URLs), more context is needed to ensure reliable 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?

The input schema has 100% description coverage, with the 'imageUrl' parameter clearly documented. The description adds no additional meaning beyond the schema, such as URL format requirements or validation rules. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 action ('display') and the resource ('generated image'), specifying it opens in a new tab. It distinguishes from siblings like 'generate-image' (which creates images) and 'add' (unrelated), but doesn't explicitly contrast with other display or viewing tools if they existed. The purpose is specific but could be more precise about the display mechanism.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a generated image URL from 'generate-image'), exclusions, or comparisons to other tools for viewing images. The context is implied (use after generation), but no explicit usage instructions are given.

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/virajsamarasinghe/MCP-Claude'

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