Skip to main content
Glama

same_energy_preview_image

Read-only

Previews a reduced candidate image and returns the larger file’s title, origin, and resolution for visual comparison; saving requires a separate save action.

Instructions

Mostra prévia de um resultado e consulta título, origem e resolução do arquivo maior.

A prévia é reduzida e serve somente para visualização. Para salvar, use save_image. Passe task_id da busca guiada; examine a política da modalidade e forneça o SHA-256 ao salvar.

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_id": "<image_id>"
    },
    "name": "same_energy_preview_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNo
image_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: the returned preview is downscaled and not intended for download, and the larger file's metadata (title, origin, resolution) is queried alongside it. The trailing advice about examining the modality policy and supplying a SHA-256 concerns the save tool rather than this call, which slightly muddies the message.

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?

Short and front-loaded: purpose and metadata scope in the first sentence, then usage and saving guidance. A small amount of redundancy in 'a prévia é reduzida e serve somente para visualização' after already saying it shows a preview, but no padding that obscures the call.

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?

An output schema exists, so return values need not be explained, and read-only behavior is covered by annotations. However, for a two-parameter tool with zero schema description coverage, the lack of any explanation of image_id leaves a gap an agent must guess at.

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 carries the burden. It explains where task_id comes from (the guided search) but says nothing about image_id, its format, or why task_id is optional. Partial compensation only.

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?

States a concrete verb and resource: showing a reduced preview of a result plus querying title, origin and resolution of the larger file. It also contrasts itself with the save path (same_energy_save_image), so an agent can tell the two apart without inspecting schemas. It is slightly vague about what a 'resultado' is, relying on the task_id/search context to imply 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?

Explicit routing guidance: the preview is for visualization only, and saving must go through save_image. It also tells the caller to pass task_id from the guided search. It stops short of stating when a preview is unnecessary or what happens if image_id belongs to a different task, but the primary when-to-use/when-not-to-use split is clear.

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