EGOS (público)

Diagnóstico: a empresa cabe IA?

diagnostico_0_infinito

Read-onlyIdempotent

Diagnóstico 'a empresa cabe IA?' em 7 dimensões. Sem argumentos: devolve o roteiro (as 7 perguntas e as âncoras de nota) para você conduzir a conversa. Com notas (uma por dimensão, com a evidência que a pessoa disse): devolve o veredito calculado por regra fixa, sem IA — mesma entrada, mesma saída. Toda resposta traz privacidade: 3 linhas (o que enviamos, o que guardamos, como apagar). Para ver ou apagar seus dados, chame meus_dados_ver. Por padrão nada do que a pessoa digita é guardado. EN: Quick check: is your company ready for AI? Seven questions, one fixed-rule verdict, no AI model involved.

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

Input Schema

Name	Required	Description	Default
`notas`	No
`meu_id`	No	O seu id (recebido em meus_dados_ver). Só serve se a pessoa escolheu guardar recibos (meus_dados_escolher).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 17, 2026

addedInput schema / properties / meu_id

Added value: +{
+  "description": "O seu id (recebido em meus_dados_ver). Só serve se a pessoa escolheu guardar recibos (meus_dados_escolher).",
+  "maxLength": 64,
+  "type": "string"
+}

changedInput schema / properties / notas / items / properties / evidencia / description

Previous value: -"O que a pessoa disse, citado."New value: +"O que a pessoa disse, citado. Não inclua CPF, dado de saúde, de cartão ou senha. / EN: what the person said, quoted; never include ID numbers, health, card or password data."

First observedOct 14, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, yet the description adds substantial context beyond them: no AI model is invoked, the verdict is computed by fixed rule ('mesma entrada, mesma saída'), every response carries a `privacidade` block, and nothing is stored by default. This determinism and privacy stance are exactly the traits annotations cannot convey.

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-loads the core function and the two modes before the privacy addendum, and each sentence earns its place. The trailing English one-liner largely restates the Portuguese content and is mildly redundant, keeping it short of a 5.

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?

With no output schema, the description does carry return-shape disclosure: it describes the roteiro, the calculated veredito, and the 3-line `privacidade` block, which is what an agent needs. Minor gaps remain around the enum domains and the `fonteApenasDecisor` flag, so it is strong but not exhaustive.

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 coverage is 50%: `evidencia` and `meu_id` are documented in-schema, while the `notas` array container is only explained in prose ('uma por dimensão, com a evidência'). The description does not clarify the `nivel` enum (vermelho/amarelo/verde), the 7 `dimensao` values, or `fonteApenasDecisor`, so it only partially compensates for the coverage gap. Baseline 3 is appropriate.

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 resource (a 7-dimension AI-readiness diagnostic) and two distinct operating modes: no-args returns the script, with `notas` returns the fixed-rule verdict. It also names a sibling (meus_dados_ver) for the adjacent data-management need, so an agent can tell this apart from the other tools without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly conditions each mode: 'Sem argumentos: devolve o roteiro... Com `notas`: devolve o veredito'. It also tells the agent where to route data access/deletion (meus_dados_ver), giving both when-to-use and a named alternative. Nothing is left to inference.

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

All EGOS (público) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?