Skip to main content
Glama

same_energy_start_task

Starts every new task by presenting three user-selectable goals for reference photos, advertising, or color grading, and records the user's choice without deciding for them.

Instructions

Comece TODA nova tarefa com este seletor. Abre 3 objetivos, sem pesquisar nem enviar fotos.

Entregue e abra a URL local. O usuário escolhe referência fotográfica, publicidade (Anúncios ou Fotos publicitárias → Produtos/Pessoas) ou color grading (Color exclusivamente / Color e temática), depois Enviar foto ou Enviar descrição. Se não houver navegador, apresente options e registre cada escolha com same_energy_task. Nunca escolha pelo usuário. initial_description só preserva um pedido já fornecido.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "same_energy_start_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
initial_descriptionNo

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 that it is non-read-only, non-destructive and closed-world. The description adds real behavioral context beyond that: it opens a local URL, requires a browser with a defined no-browser fallback, must never choose on the user's behalf, and hands off recording to same_energy_task. It does not say what the call returns, which is the only notable gap.

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 instruction is front-loaded, but the middle paragraph crams an entire option tree ('Anúncios ou Fotos publicitárias → Produtos/Pessoas', 'Color exclusivamente / Color e temática') into one dense run-on that is hard to parse and partially duplicates the fallback instruction.

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?

For a one-parameter entry-point tool with no output schema and only partial annotations, the description covers invocation, fallback, and parameter meaning. It omits what the tool returns (a handle, a URL, or nothing) and what the agent should do with the result after the user selects, which matters for an orchestration entry point.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter has 0% schema description coverage, so the description carries the burden. It does so by stating 'initial_description só preserva um pedido já fornecido', which meaningfully constrains the parameter to preserving an existing request rather than authoring a new one.

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 role: 'Comece TODA nova tarefa com este seletor' plus what the selector presents (photographic reference, advertising, color grading). It distinguishes itself from search/upload flows by saying it does not search or send photos, though 'abre 3 objetivos' remains somewhat opaque about what an 'objetivo' actually is.

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 clear trigger ('every new task'), a negative constraint (do not search or send photos here), and a concrete fallback path: if no browser, present options and record each choice with same_energy_task. It stops short of naming any sibling tool as the alternative for edge cases, but the routing is otherwise explicit.

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