Skip to main content
Glama

same_energy_get_gallery

Read-only

Retrieve an existing image gallery without resending the reference photo, then preview limited candidates for visual screening and selection.

Instructions

Retoma a galeria sem reenviar a foto; candidatas grandes ainda exigem triagem visual.

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": {
      "gallery_url": "<gallery_url>"
    },
    "name": "same_energy_get_gallery"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
task_idNo
gallery_urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds one genuine behavioral note — that large candidate sets still require visual triage — but says nothing about what the call returns, whether state is mutated, or what happens with an invalid/expired gallery_url.

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?

One compact sentence with the key constraint ('sem reenviar a foto') front-loaded ahead of the triage caveat. No filler, though the brevity comes partly at the cost of the missing details noted elsewhere.

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?

The existence of an output schema means return values needn't be described, and read-only annotations cover safety. Still, for a 3-parameter tool with zero schema coverage and an ambiguous relationship to search_task siblings, the definition leaves too much undefined to be called complete.

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%, so the description carries the full burden, yet it explains only the gallery concept at a high level. The limit (1-50, default 24), the nullable task_id, and the required gallery_url format are all left undocumented in both schema and prose.

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 names a verb and resource ('Retoma a galeria') and clarifies that the photo is not resent, which hints at a reuse/continuation operation. However, it never states what a 'galeria' actually is (prior search results? a task's candidate set?) and does not distinguish this tool from siblings like same_energy_search_by_image or same_energy_task.

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?

'Sem reenviar a foto' implicitly signals when to use this instead of re-running an image search, which is useful context. But it is only implied — no explicit when-to-use, prerequisites, or named alternative tool is given, so the agent must infer the routing decision.

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