Skip to main content
Glama
Sign In
OpenMonetis MCP

OpenMonetis MCP

by Welington98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Snapshot completo do dashboard

get_dashboard_snapshot
Read-onlyIdempotent

Retrieve all dashboard sections for a month in one call—metrics, balances, payment status, expense breakdowns, and per-person expenses—when you need a complete financial overview.

Instructions

Retorna de uma vez todas as seções do dashboard de um mês: métricas, saldos das contas, status de pagamentos, distribuição de despesas por condição/forma de pagamento, quebra por categoria e despesas por pessoa. Payload maior que get_dashboard_overview; use quando precisar de uma visão completa em uma única chamada.

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_snapshot"
  }
}

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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior the annotations can't convey: this is an aggregation of many sections and returns a heavier payload than the overview, which matters for context budgeting. It stops short of quantifying size or stating latency, so 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.

Conciseness5/5

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

Two sentences, front-loaded with the enumeration of contents and closed with the disambiguation. The long list is load-bearing because there is no output schema, and every clause names a distinct returned section.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the burden of describing return content, and it does so section by section. Combined with a fully documented single parameter and complete annotations, an agent has everything needed to decide and call correctly.

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?

The single parameter is fully documented in the schema at 100% coverage, including the YYYY-MM pattern and the omit-for-current-month default. The description says the snapshot is scoped to "um mês" but adds no syntax or default behavior beyond the schema, so the baseline 3 applies.

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 and resource ("Retorna ... todas as seções do dashboard de um mês") and then enumerates the exact sections returned: métricas, saldos, status de pagamentos, distribuição, categorias, despesas por pessoa. It explicitly distinguishes itself from the sibling get_dashboard_overview by payload size, so an agent needn't open either schema to choose.

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?

The final sentence gives explicit selection guidance: use it when you need a complete view in a single call, and it contrasts that with get_dashboard_overview at the cost of a larger payload. The when-to-use condition and the alternative are both stated rather than inferred.

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