Skip to main content
Glama

same_energy_create_catalog

Create or reopen a local HTML catalog for an already saved search folder, showing images in a tagged, filterable grid so you can mark and move selections.

Instructions

Cria ou reabre o catálogo padrão de uma pasta de busca já salva, sem nova pesquisa.

search_directory: pasta output_AAAA-MM-DD_nome-da-busca, nunca a pasta base. Não move imagens nesta chamada. Retorna URL local e catalogo.html; exige Docker em execução. Todas as imagens da raiz aparecem na mesma página, com marcação e filtro de marcadas. O botão fixo move as marcadas para selecionadas/ sem sobrescrever arquivos. A grade principal não lê selecionadas/; há uma aba separada para essa pasta. Os JSONs permanecem em json/. Entregue e abra a URL ao finalizar o salvamento.

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": {
      "search_directory": "<search_directory>"
    },
    "name": "same_energy_create_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
search_directoryYes

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 only declare non-read-only, non-destructive, closed-world; the description adds what is actually written (catalogo.html, JSONs kept in json/), that this call does not move images, and that it returns a local URL requiring a running Docker. That is substantive context beyond the annotations, though it never says what happens when reopening an existing catalog versus creating a fresh one.

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 core purpose and the directory constraint are front-loaded and useful. However, several lines describe downstream UI behavior ('O botão fixo move as marcadas', 'A grade principal não lê selecionadas/', the separate tab) that does not affect how this tool is invoked, padding an otherwise lean definition.

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?

For a file-writing tool with no output schema, the description covers the return values (local URL and catalogo.html), the environment prerequisite, the side-effect boundary, and the output layout. The remaining gap is the semantics of 'title' and the create-vs-reopen difference, which is minor but not trivial.

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 0%, so the description must carry parameter meaning. It does well for search_directory (accepted naming pattern, prohibition on the base folder), but the optional 'title' parameter is never mentioned, leaving one of two parameters undocumented in both schema and description.

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 specific verb and resource ('Cria ou reabre o catálogo padrão') plus a scope constraint ('de uma pasta de busca já salva, sem nova pesquisa') that separates it from the search siblings. An agent can tell this is catalog generation over an existing folder, not a new search, although no sibling is named explicitly.

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?

Gives a hard precondition on which directory to pass ('output_AAAA-MM-DD_nome-da-busca, nunca a pasta base'), states that no new search is performed, and adds an environment prerequisite ('exige Docker em execução') and a follow-up action ('Entregue e abra a URL ao finalizar'). It does not compare against alternatives such as same_energy_get_gallery, so the routing is implied rather than explicit.

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