Skip to main content
Glama

same_energy_check_updates

Read-only

Checks public GitHub for available updates without a token and reports whether an install is possible; it never installs and only prepares the update after explicit approval using the target SHA.

Instructions

Consulta o GitHub público sem token. Se houver novidade, diga: Tem atualização, posso instalar?

Não instala nada. Após concordância explícita, prepare a atualização com o target_sha apresentado.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 already declare readOnlyHint=true and openWorldHint=true, and the description adds genuinely new behavior: unauthenticated public GitHub access, no installation occurs, an explicit confirmation gate, and the presentation of a target_sha. It does not describe return content beyond target_sha, but the safety and side-effect profile is well covered.

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?

Very short and front-loaded with the operation; the confirmation-gate sentence earns its place because it constrains agent behavior. The embedded suggested phrase ("Tem atualização, posso instalar?") is borderline filler but does encode the intended user interaction.

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 zero-parameter, read-only check with no output schema, the description covers what it touches (public GitHub, no token), what it will not do (install), and how the workflow continues. The only meaningful omission is the name of the follow-up tool to invoke after user consent.

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?

With zero parameters the baseline is 4, and there is nothing in the schema needing elaboration. Mentioning that target_sha is surfaced to the caller usefully foreshadows the value needed for the next step.

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 description states a specific action and source ("Consulta o GitHub público sem token") and, via "Se houver novidade", implies an update-availability check, which aligns with the tool name. It never names a sibling, but the check-vs-prepare split is discernible from the text itself.

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?

It clearly marks the boundaries of this step (does not install, requires explicit user agreement before moving on) and describes a two-step flow. However, the follow-up step ("prepare a atualização") is never tied to a specific tool name, so the agent must guess which sibling to call after confirmation.

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