Skip to main content
Glama

same_energy_search_by_text

Search for real visual references by text description and return large candidate images with confirmed resolution for review.

Instructions

Em nova tarefa retorna o seletor guiado; execute same_energy_run_task após concluir.

Busca por descrição; retorna candidatas grandes com resolução confirmada, sem triagem visual.

Examine as candidatas e descarte imagens não fotográficas, com marcações ou claramente geradas por IA. Pergunte ao usuário a pasta para salvar nesta busca antes de chamar save_image.

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": {
      "query": "<query>"
    },
    "name": "same_energy_search_by_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is partly covered; the description adds genuinely non-obvious behavior: candidates come back large and resolution-confirmed and are NOT visually triaged, so the agent must do the filtering (discard non-photographic, marked, or AI-generated images). It also discloses a user-interaction step before save_image, which is real operational context rather than schema restatement.

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 sentences, each carrying distinct information (workflow hook, purpose, post-filtering duty, save prerequisite). Slight weakness: it opens with the task-state note rather than the purpose, so the core 'what it does' is not front-loaded.

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?

An output schema exists, so return shape need not be explained, and the description instead covers the parts an agent would otherwise get wrong: the run_task follow-up, the manual visual vetting of results, and asking the user for a save folder. The undocumented 'limit' parameter is the main remaining gap for a simple two-parameter tool.

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% for two parameters, so the description must carry the burden. 'Busca por descrição' gives some sense of what 'query' accepts (a description), but it never clarifies natural language vs keywords, language, or expected length, and the 'limit' parameter (1-50, default 12) is not mentioned at all.

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?

The second sentence gives a specific verb and resource: a text-description search that returns large, resolution-confirmed candidate images without visual triage. The phrase 'Busca por descrição' implicitly separates it from same_energy_search_by_image, though that sibling is never named, so discrimination requires a small inference.

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 states the workflow context ('Em nova tarefa') and the mandatory follow-up ('execute same_energy_run_task após concluir'), plus a prerequisite for saving ('Pergunte ao usuário a pasta... antes de chamar save_image'). It does not explicitly say when to prefer this over the image-based search sibling, leaving that to the 'por descrição' hint.

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