Skip to main content
Glama

same_energy_help

Read-only

Returns guided help, usage examples, and next steps for the SAME-ENERGY MCP server, clarifying its workflow for finding visual references.

Instructions

Use quando a pessoa perguntar 'como funciona o mcp SAME-ENERGY?' ou pedir ajuda.

Retorna orientação assistida, exemplos e próximos passos. Não pesquisa, envia ou salva imagens.

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_help"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is partly covered. The description adds real value beyond that by stating the tool performs no searching, sending, or saving of images — an explicit no-side-effect guarantee — and by describing the return content (guidance, examples, next steps). It does not discuss output format or length, but for a zero-parameter help tool that is a minor gap.

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

Conciseness5/5

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

Two short sentences plus a scope boundary, with the trigger condition front-loaded and zero filler. Every clause either tells the agent when to call it or what it will and will not do.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple, zero-parameter help tool with a truthful read-only annotation set and no output schema. The description supplies the trigger, the return content, and the negative scope, which is everything an agent needs to select and invoke it correctly.

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 tool takes no input parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. The description correctly implies no arguments are needed to obtain help.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Retorna orientação assistida, exemplos e próximos passos') and immediately scopes it against the sibling family with 'Não pesquisa, envia ou salva imagens.' An agent can tell this is the documentation/help entry point rather than any of the image-search, save, or task tools.

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?

There is an explicit trigger condition: use it when the person asks how the SAME-ENERGY MCP works or asks for help. It also gives a negative boundary (no searching, sending, or saving images), which implicitly routes those requests elsewhere. It does not name a specific alternative sibling, so it falls short of a full when/when-not/alternatives statement.

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