Skip to main content
Glama

Arc Flash Platform — Estudos Elétricos

Solicitar orçamento de estudo/laudo (ART)

solicitar_orcamento

Encaminha um pedido de ORÇAMENTO de estudo/laudo assinável com ART (arc flash, curto-circuito, seletividade, adequação NR-10) direto do chat. Informe o e-mail de contato e o escopo (ex.: nº de painéis, classe de tensão, prazo, cidade). A equipe responde pelo e-mail informado. Não consome o limite das calculadoras e funciona inclusive quando o uso gratuito do dia esgotou.

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": {
      "email": "<email>"
    },
    "name": "solicitar_orcamento"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomeNo
emailYes
escopoNo
api_keyNo
empresaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag a non-read-only, open-world, non-idempotent call; the description adds real behavior beyond them: the request is handled by a human team replying to the supplied e-mail, and it bypasses the calculator quota and daily free-usage limits. It does not discuss duplicate submissions or expected response time, which is why it is not a 5.

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?

Front-loaded with the action and resource, then the required inputs, then the outcome and quota caveat; every sentence contributes. The parenthetical scope examples are dense but useful rather than filler.

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?

There is no output schema, so the description correctly explains what happens next (team replies by e-mail) and the quota behavior. For a 5-parameter form-submission tool it still leaves gaps: the role of api_key, whether repeated calls create duplicate requests, and any expected turnaround are unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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. It does explain the two most important inputs — e-mail as the contact channel and 'escopo' with concrete examples (nº de painéis, classe de tensão, prazo, cidade) — but leaves nome, empresa and especially api_key entirely unaddressed, so half the parameters remain undocumented.

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?

States a specific verb ('Encaminha um pedido de ORÇAMENTO') and resource ('estudo/laudo assinável com ART'), and enumerates the study types covered (arc flash, curto-circuito, seletividade, NR-10), which clearly separates it from the sibling calculadora_* 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?

Explains the context in which to use it ('direto do chat', after informing e-mail and scope) and gives a concrete routing rule: it does not consume calculator limits and works even when the free daily quota is exhausted — implicitly telling the agent to use this instead of a calculator when the user wants a quote. No explicit 'when not to use' or named alternative, so not a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources