Skip to main content
Glama

same_energy_run_task

Runs a visual or color search from a saved brief and reference photo, returning candidate images plus a task_id and visual policy for previewing, reviewing, and saving results.

Instructions

Pesquisa SOMENTE após o usuário concluir o seletor (ready=true).

Usa o brief salvo; envia a foto ao Same Energy nos modos por semelhança. Color exclusivamente por foto usa apenas a paleta local numa busca textual, reordenada por cor; não envia a foto nem exige a mesma temática. Retorna candidatas, task_id e a política visual da modalidade; inspecione-as. Passe task_id em get_gallery, preview_image e save_image. Pergunte a pasta antes de salvar e não presuma a triagem visual de anúncio, produto, pessoa ou color.

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": {
      "task_id": "<task_id>"
    },
    "name": "same_energy_run_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
task_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses that similarity modes send the photo to the external Same Energy service while the color mode does not send the photo and works only on the local palette. It also warns not to presume visual triage of ad/product/person/color, which is useful behavioral context. It does not explain the side effects of task creation implied by readOnlyHint=false beyond returning a task_id.

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

Conciseness3/5

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

The precondition is front-loaded, which is good, but the text is dense and mixes return-value description, cross-tool routing, and save-time instructions in one block. Several sentences carry useful content, yet the structure would benefit from separating mode behavior from routing advice.

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, yet the description still lists them; meanwhile the essential unknown — where task_id comes from and what limit does — is left uncovered. For a two-parameter task-launch tool with an external side effect, this leaves a meaningful gap.

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?

Schema description coverage is 0% and the description does not compensate: it tells the agent to pass task_id to other tools but never says where task_id originates, and the limit parameter is never mentioned at all. Only the task_id requirement is implicitly referenced, leaving half the parameters without semantic guidance.

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 description uses the verb 'Pesquisa' (search) and describes what the task does for each mode (similarity vs. color-by-photo), plus a precondition (ready=true). However, it never clearly distinguishes this tool from the sibling tools same_energy_search_by_image or same_energy_search_by_text, and it mixes mode behavior with routing instructions, so the core purpose is only implied.

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?

It states a real precondition ('Pesquisa SOMENTE após o usuário concluir o seletor (ready=true)') and gives downstream routing ('Passe task_id em get_gallery, preview_image e save_image') plus an instruction to ask about the folder before saving. It does not say when to prefer this tool over the sibling search tools or what to do when ready=false, so guidance is only partial.

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