Skip to main content
Glama

status_conexao

Checks whether the MCP connection and Java calculator API are online, starting, offline, or in error; reports database version and log location; and starts a stopped API in the background.

Instructions

Mostra se está tudo conectado: o MCP ligado ao Claude, a API Java da calculadora (online, iniciando, offline ou erro), a versão do banco de dados e onde ver os logs.

Use quando o usuário perguntar se a calculadora está funcionando, ou quando outra ferramenta falhar por conexão. Se a API estiver parada, ela é iniciada em segundo plano.

Args: iniciar_se_offline: Se a API estiver parada, iniciar em segundo plano (padrão: sim).

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": "status_conexao"
  }
}

Input Schema

NameRequiredDescriptionDefault
iniciar_se_offlineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it discloses the critical non-obvious trait: if the API is offline it will be started in the background, making this a potentially mutating call despite its 'status' name. It also enumerates the possible API states returned and points to logs, though it says nothing about permissions or timing of the background start.

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?

The structure is sensible — what it reports, when to use it, side effect, then the argument — and the key side-effect sentence is short and prominent. The opening sentence packs multiple sub-items into a long clause, which is slightly dense but not wasteful.

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?

For a single-parameter tool with no output schema and no annotations, the description covers what an agent needs: what is checked, the possible states, the auto-start side effect, when to call it, and where logs live. Nothing essential to correct invocation is missing.

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?

Schema description coverage is 0%, so the description must compensate, and it does: the Args block explains that iniciar_se_offline controls whether a stopped API is launched in the background and restates the default. The schema already carries `default: true`, so the addition is real but modest rather than fully clarifying (e.g., no note on what is returned when it is false).

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 diagnostic resource and enumerates exactly what it reports: MCP-to-Claude linkage, Java API state (online, starting, offline, error), database version, and log location. This is clearly distinct from the fifteen sibling tools, which all deal with tax calculation, classification, and lookups.

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 gives two concrete trigger conditions — the user asking whether the calculator works, or another tool failing with a connection error — which is strong routing guidance. It stops short of stating when not to call it (e.g., distinguishing a data error from a connection error), so it falls just short of a 5.

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