Skip to main content
Glama

same_energy_status

Read-only

Checks that the site, isolated browser, and local folder are accessible without login, confirming the environment is ready for use.

Instructions

Verifica site, navegador isolado e pasta acessível. Não exige login.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: no login/authentication is required and the check touches an isolated browser and a local folder, hinting at environmental side effects. It does not describe the shape of the result or how failures are reported.

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, no filler, with the check targets stated first and the no-login precondition second. Nothing could be removed without losing information.

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 diagnostic with no output schema, the description covers what is inspected and the auth requirement. The only meaningful gap is that it does not indicate what a result or a failed check looks like, which matters somewhat given no output schema exists.

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 zero parameters, so there is nothing in the schema semantics for the description to clarify. Baseline 4 applies; the description correctly implies a single call with no arguments.

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 names a concrete diagnostic verb ("Verifica") and three specific resources it inspects: site, isolated browser, and accessible folder. An agent can tell this is a health/status probe rather than an action tool, though it stops short of stating explicitly that a status report is returned.

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?

The description gives an implicit trigger — this is the tool to run to confirm the environment is ready — and the note "Não exige login" implies it can be called before authentication. It offers no explicit when-to-use or when-not-to-use comparison against siblings such as same_energy_help or same_energy_check_updates.

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