Skip to main content
Glama

rotation-info

Extract rotation and flip orientation data from images to analyze and correct image alignment issues using EXIF metadata.

Instructions

Get detailed rotation and flip information from image orientation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYes

Implementation Reference

  • The main handler function that loads the image buffer using loadImage and retrieves rotation/flip info using exifr.rotation.
    async (args, extra) => {
      try {
        const { image } = args;
        const buf = await loadImage(image);
        const rotation = await exifr.rotation(buf);
        
        if (!rotation) {
          return createErrorResponse('No rotation metadata found in image');
        }
        
        return createSuccessResponse(rotation);
      } catch (error) {
        return createErrorResponse(`Error reading rotation info: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • Registers the 'rotation-info' tool on the MCP server with name, description, input schema, and handler function.
    // Tool 9: rotation-info - gets rotation and flip information
    const rotationInfoTool = server.tool('rotation-info',
      "Get detailed rotation and flip information from image orientation",
      {
        image: ImageSourceSchema
      },
      async (args, extra) => {
        try {
          const { image } = args;
          const buf = await loadImage(image);
          const rotation = await exifr.rotation(buf);
          
          if (!rotation) {
            return createErrorResponse('No rotation metadata found in image');
          }
          
          return createSuccessResponse(rotation);
        } catch (error) {
          return createErrorResponse(`Error reading rotation info: ${error instanceof Error ? error.message : String(error)}`);
        }
      }
    );
    tools['rotation-info'] = rotationInfoTool;
  • Zod schema defining the input 'image' parameter as ImageSource (path, url, base64, or buffer).
    const ImageSourceSchema = z.object({
      kind: z.enum(['path', 'url', 'base64', 'buffer']),
      path: z.string().optional(),
      url: z.string().optional(),
      data: z.string().optional(),
      buffer: z.string().optional()
    });
  • Helper function to load image data into buffer from various source types, used in the handler.
    export async function loadImage(src: ImageSourceType): Promise<Buffer | Uint8Array> {
      try {
        switch (src.kind) {
          case 'path':
            if (!src.path) {
              throw new Error('Path is required for kind="path"');
            }
            return await fs.promises.readFile(src.path);
          
          case 'url':
            if (!src.url) {
              throw new Error('URL is required for kind="url"');
            }
            
            if (src.url.startsWith('file://')) {
              // Handle file:// URLs by converting to filesystem path
              const filePath = fileURLToPath(src.url);
              return await fs.promises.readFile(filePath);
            } else {
              // Handle HTTP/HTTPS URLs
              const response = await fetch(src.url);
              if (!response.ok) {
                throw new Error(`Failed to fetch URL: ${response.status} ${response.statusText}`);
              }
              return new Uint8Array(await response.arrayBuffer());
            }
          
          case 'base64':
            if (!src.data) {
              throw new Error('Data is required for kind="base64"');
            }
            
            // Check for potential oversized base64 string (>30MB)
            if (src.data.length > 40000000) { // ~30MB in base64
              throw new Error('PayloadTooLarge: Base64 data exceeds 30MB limit');
            }
            
            // Handle data URIs or raw base64
            if (src.data.startsWith('data:')) {
              const base64Data = src.data.split(',')[1];
              return Buffer.from(base64Data, 'base64');
            } else {
              return Buffer.from(src.data, 'base64');
            }
          
          case 'buffer':
            if (!src.buffer) {
              throw new Error('Buffer is required for kind="buffer"');
            }
            return Buffer.from(src.buffer, 'base64');
          
          default:
            // This should never happen due to type constraints, but TypeScript needs it
            throw new Error(`Unsupported image source kind: ${(src as any).kind}`);
        }
      } catch (error) {
        if (error instanceof Error) {
          throw new Error(`Failed to load image: ${error.message}`);
        }
        throw error;
      }
    }
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 it 'gets' information, implying a read-only operation, but doesn't clarify if it requires specific permissions, handles errors, or has performance constraints like rate limits. The description is minimal and lacks behavioral context beyond the basic action.

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 purpose without unnecessary words. It's front-loaded and appropriately sized for a simple tool, with no wasted information.

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 moderate complexity (1 parameter with nested objects), no annotations, no output schema, and 0% schema description coverage, the description is insufficient. It doesn't explain return values, error handling, or input semantics, making it incomplete for effective agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, and the tool description adds no parameter information. It doesn't explain what 'image' represents, the meaning of 'kind' values (path, url, base64, buffer), or how to structure the input object, leaving parameters largely undocumented.

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 verb 'Get' and the resource 'detailed rotation and flip information from image orientation', making the purpose understandable. It distinguishes this tool from siblings like 'gps-coordinates' or 'read-exif' by focusing specifically on orientation data, though it doesn't explicitly compare to alternatives like 'orientation'.

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 sibling tools like 'orientation' or 'read-metadata', nor does it specify prerequisites or contexts for usage, leaving the agent to infer appropriate scenarios.

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/stass/exif-mcp'

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