Skip to main content
Glama
Sign In
OpenMonetis MCP

OpenMonetis MCP

by Welington98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Visão geral do mês

get_dashboard_overview
Read-onlyIdempotent

Retrieve monthly financial dashboard metrics—revenue, expenses, balance, projections, prior-month comparison, and six-month history—to assess a period's financial situation.

Instructions

Retorna as métricas do dashboard financeiro de um mês: receitas, despesas, saldo, valor projetado, comparação com o mês anterior e histórico dos últimos 6 meses. Use como primeira ferramenta para entender a situação financeira do período.

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

Input Schema

NameRequiredDescriptionDefault
periodNoMês de referência no formato YYYY-MM. Omita para usar o mês atual.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the payload contents — including the prior-month comparison and 6-month history — which is important since there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste. The returned metrics come first and the usage cue follows, so the most decision-relevant information is front-loaded.

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?

For a read-only, single-optional-parameter tool with no output schema, the description does the necessary work by enumerating the metrics returned and the temporal scope. Only the absence of any pagination or data-freshness note keeps it from a 5.

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 100%: the single `period` parameter already documents the YYYY-MM format and the default-to-current-month behavior. The description adds no additional parameter semantics beyond noting the month scope, so the baseline 3 applies.

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 names a specific verb and resource ("Retorna as métricas do dashboard financeiro") and enumerates the exact metrics returned: receitas, despesas, saldo, valor projetado, comparação mensal e histórico de 6 meses. It does not explicitly differentiate itself from siblings like get_dashboard_attention or get_dashboard_snapshot, which keeps it below a 5.

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?

"Use como primeira ferramenta para entender a situação financeira do período" gives clear entry-point guidance on when to reach for this tool. It stops short of naming alternatives or stating when not to use it, so it is not a full 5.

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