Skip to main content
Glama
Sign In
OpenMonetis MCP

OpenMonetis MCP

by Welington98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Diagnósticos de IA

list_ai_diagnoses
Read-onlyIdempotent

List AI-generated financial diagnoses with period, provider, status, and financial health to review past assessments and track financial condition.

Instructions

Lista os diagnósticos financeiros gerados por IA, com período, provedor, status e saúde financeira.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds that results include period, provider, status, and financial health, which hints at the shape of the returned record. It says nothing about pagination, ordering, result limits, or whether the list can be empty, which is a modest gap for a list tool.

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?

It is a single front-loaded sentence with no filler, starting with the verb 'Lista'. The clause 'com período, provedor, status e saúde financeira' is slightly ambiguous: it could be read as filtering criteria rather than returned fields, costing a point.

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?

This is a low-complexity, zero-parameter, read-only listing tool with no output schema. The description partially compensates for the absent output schema by enumerating the fields returned. Only pagination and empty-result behavior are left implicit, acceptable for this tool's simplicity.

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 no parameters, so there is nothing to disambiguate; this sets the baseline at 4. The description's mention of 'período, provedor, status e saúde financeira' describes returned fields, not inputs, which is useful but not required by the schema.

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 gives a specific verb and resource in Portuguese: 'Lista os diagnósticos financeiros gerados por IA'. This clearly distinguishes it from sibling tools that fetch or mutate a single diagnosis, such as get_ai_diagnosis or create_ai_diagnosis, though the text never names those siblings.

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 implies a bulk-listing context by using 'Lista', but it states no explicit conditions for when to use this tool instead of get_ai_diagnosis, which appears to retrieve a single diagnosis. An agent can infer the difference from the names alone; however, the description adds no routing guidance of its own.

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

Deploy Server

Other Tools