Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Detalhar diagnóstico de IA

get_ai_diagnosis
Read-onlyIdempotent

Retrieves a complete diagnosis for a specified ID, including status, results, attention points, and failure details when applicable.

Instructions

Retorna um diagnóstico completo, incluindo status, resultado, pontos de atenção e falha quando houver.

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": {
      "id": "<id>"
    },
    "name": "get_ai_diagnosis"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare a safe, idempotent, closed-world read, so the safety profile is covered. The description adds real value by enumerating the returned fields ('falha quando houver' signals an optional failure field), but says nothing about behavior on a nonexistent ID, permissions, or freshness of the diagnosis.

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?

A single well-formed sentence with no filler, and the core action ('Retorna um diagnóstico completo') is front-loaded before the field list. Nothing is redundant.

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?

For a one-parameter read tool with full annotation coverage and no output schema, the description usefully sketches the return shape. The remaining gap is the undisclosed identity/meaning of the required 'id' parameter, which is the main thing an agent must get right to call it.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions the sole parameter 'id' — not what entity it identifies, nor that it is the diagnosis UUID. The format/pattern in the schema only tells the agent it is a UUID, not whose ID it is.

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?

States a specific verb ('Retorna') and resource ('diagnóstico completo') and enumerates the payload (status, resultado, pontos de atenção, falha), which separates it from list_ai_diagnoses. It stops short of saying it retrieves a single diagnosis by its ID, leaving that to be inferred from the tool name and title.

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

Usage Guidelines2/5

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

No when-to-use guidance at all: nothing distinguishes it from list_ai_diagnoses or get_ai_status, and no prerequisites or conditions are given. The agent must infer usage purely from the name.

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