Skip to main content
Glama
Sign In
Image MCP

Image MCP

by Expert-Integrado
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Informações da imagem

get_image_info

Returns dimensions, format, disk size, and transparency of a local image to prepare it for editing, conversion, or publication.

Instructions

Retorna dimensões, formato, tamanho em disco e transparência de uma imagem local. Útil antes de editar, converter ou publicar.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "image": "<image>"
    },
    "name": "get_image_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesCaminho absoluto da imagem

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior3/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 accurately describes the read-only nature (returns info) and the type of data returned. However, it lacks details on missing files, error handling, or disk access behavior, which is acceptable for a simple tool but not exhaustive.

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 extremely concise—two sentences that front-load the tool's output and usage context. Every word adds value; no waste.

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 the tool's low complexity (one parameter, no nested objects, no output schema), the description is largely complete. It covers purpose, return values, and usage context. A slight improvement could be to mention the return format, but this is not essential.

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 coverage is 100%, so the schema already documents the lone parameter. The description does not add extra meaning beyond what the schema provides (absolute path). Baseline score of 3 is appropriate.

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 returns specific metadata (dimensions, format, disk size, transparency) for a local image. It uses a specific verb and resource, distinguishing it from sibling tools which perform actions like editing, converting, or generating images.

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 recommends using this tool before editing, converting, or publishing, providing clear usage context. However, it does not state when not to use it or mention alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools