Skip to main content
Glama

describe

Generate AI descriptions of images using vision providers like Gemini, OpenAI, or Claude. Specify detail level and optional prompts for customized analysis.

Instructions

Get an AI-generated description of an image. Supports multiple providers (Gemini, OpenAI, Claude).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYesPath to the image file
promptNoOptional question or instruction for the description
providerNoVision provider to use (default: gemini)
detailNoLevel of detail in the description (default: detailed)

Implementation Reference

  • The handleDescribe function that executes the 'describe' tool: processes input args, converts image to base64, delegates to the selected provider's describe function (gemini, openai, or claude), and returns the generated description as text content.
    export async function handleDescribe(args: Record<string, unknown>) {
      const image = args.image as string;
      const prompt = args.prompt as string | undefined;
      const provider = (args.provider as Provider) || "gemini";
      const detail = (args.detail as "brief" | "detailed") || "detailed";
    
      const { base64, mimeType } = await imageToBase64(image);
    
      let description: string;
    
      switch (provider) {
        case "gemini":
          description = await geminiDescribe(base64, mimeType, prompt, detail);
          break;
        case "openai":
          description = await openaiDescribe(base64, mimeType, prompt, detail);
          break;
        case "claude":
          description = await claudeDescribe(base64, mimeType, prompt, detail);
          break;
        default:
          throw new Error(`Unknown provider: ${provider}`);
      }
    
      return {
        content: [
          {
            type: "text",
            text: description,
          },
        ],
      };
    }
  • The describeTool object defines the tool's metadata, including name, description, and inputSchema for parameter validation.
    export const describeTool: Tool = {
      name: "describe",
      description:
        "Get an AI-generated description of an image. Supports multiple providers (Gemini, OpenAI, Claude).",
      inputSchema: {
        type: "object",
        properties: {
          image: {
            type: "string",
            description: "Path to the image file or URL (http/https)",
          },
          prompt: {
            type: "string",
            description: "Optional question or instruction for the description",
          },
          provider: {
            type: "string",
            enum: ["gemini", "openai", "claude"],
            description: "Vision provider to use (default: gemini)",
          },
          detail: {
            type: "string",
            enum: ["brief", "detailed"],
            description: "Level of detail in the description (default: detailed)",
          },
        },
        required: ["image"],
      },
    };
  • src/index.ts:37-46 (registration)
    Registration of the describeTool in the MCP server's listTools request handler, making it available for discovery.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          describeTool,
          detectTool,
          describeRegionTool,
          analyzeColorsTool,
        ],
      };
    });
  • src/index.ts:54-56 (registration)
    Dispatch in the server's CallToolRequestSchema handler that routes 'describe' tool calls to the handleDescribe function.
    case "describe":
      return await handleDescribe(args);
    case "detect":
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions support for multiple providers, which adds some context, but lacks details on behavioral traits such as rate limits, authentication needs, error handling, or what the output looks like (e.g., format, length). For a tool with no annotations, this is a significant gap in transparency.

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 two sentences, front-loaded with the core purpose, and efficiently mentions provider support without unnecessary details. Every sentence contributes directly to understanding the tool's functionality, with zero waste or redundancy.

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

Completeness3/5

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

Given 4 parameters, no annotations, and no output schema, the description is adequate but incomplete. It covers the basic purpose and provider context, but lacks details on output format, error cases, or integration with sibling tools. For a tool of this complexity, more contextual information would be beneficial to ensure proper usage.

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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema by mentioning provider support, but doesn't elaborate on parameter meanings, interactions, or usage examples. Baseline 3 is appropriate as the schema handles most of the parameter documentation.

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 tool's purpose: 'Get an AI-generated description of an image.' It specifies the action (get description) and resource (image), but doesn't explicitly differentiate from sibling tools like 'describe_region' or 'detect' which might have overlapping functionality.

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

Usage Guidelines3/5

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

The description mentions 'Supports multiple providers (Gemini, OpenAI, Claude),' which implies usage context for provider selection. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'describe_region' or 'analyze_colors,' nor does it specify scenarios where this tool is preferred or excluded.

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/simen/mcp-see'

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