Skip to main content
Glama

same_energy_search_by_image

Search Same Energy by a reference image to find visually similar photos. Use the guided selector, then send the chosen image for native similarity search and review returned candidates.

Instructions

Em nova tarefa retorna o seletor guiado sem ler ou enviar a imagem.

Após a orientação, same_energy_run_task envia a imagem ao Same Energy e usa a busca nativa por semelhança.

image_path: caminho absoluto de JPEG, PNG, GIF ou BMP de até 20 MiB na pasta montada. O arquivo é transmitido para https://same.energy. Não altera a foto local. Retorna candidatas; faça a triagem visual de fotografias sem marcações ou geração clara por IA.

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_path": "<image_path>"
    },
    "name": "same_energy_search_by_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
image_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (openWorldHint=true, destructiveHint=false), the description discloses real side effects: the file is uploaded to https://same.energy, the local photo is not modified, and formats and a 20 MiB size limit are stated. It also flags that the first call only returns a selector, which an agent could not infer from the schema alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short lines, front-loaded with the key sequencing caveat, then the parameter constraint, then a triage note. Little waste, though the opening sentence's meaning depends on knowing what a 'tarefa' is in this server.

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?

Return values need little explanation because an output schema exists, and the description still adds a visual-triage note (reject watermarked or AI-generated photos). The remaining hole is the undocumented limit parameter and the ambiguity about what the first call actually yields.

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 0%, so the description must compensate. It fully documents image_path (absolute path, JPEG/PNG/GIF/BMP, 20 MiB, mounted folder), but says nothing about limit (default 12, max 50), leaving half the parameters undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name promises an image search, but the description says this call actually 'retorna o seletor guiado sem ler ou enviar a imagem' and that the real similarity search happens in same_energy_run_task. That sequencing detail is valuable, but it leaves the agent unsure whether this tool performs the search or only prepares it.

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?

It explicitly names same_energy_run_task as the step that transmits the image after the guidance, giving a clear call order. It offers no guidance on when to prefer same_energy_search_by_text over this tool, so the choice between the two search modes is left unstated.

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