Skip to main content
Glama
Sign In
OpenMonetis MCP

OpenMonetis MCP

by Welington98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Distribuição financeira

get_financial_distribution
Read-onlyIdempotent

Retrieve monthly income and expense distribution by category, payment method, and condition for an admin, all people, or a specific person; include forecast values when needed.

Instructions

Retorna a distribuição das despesas e receitas de um mês por categoria, forma de pagamento e condição, no escopo do administrador ou de todas as pessoas. mode: "forecast" inclui valores previstos.

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": {
      "period": "<period>"
    },
    "name": "get_financial_distribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoactual
periodYes
personScopeNoEscopo: "admin" (padrão), "all" ou o ID de uma pessoa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare a safe, idempotent, closed-world read, so the safety profile needs no restating. The description adds one genuinely useful behavioral fact, that mode "forecast" folds predicted values into the distribution, plus the grouping dimensions of the result; it does not cover permissions requirements or response shape, which is acceptable only because annotations carry the operational profile.

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?

A single dense sentence that front-loads the resource and its breakdown dimensions, then adds the forecast modifier. No filler, no redundancy with the title, and the most decision-relevant facts come first.

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 three-parameter read-only aggregation with no output schema, the description supplies the grouping dimensions, the mode semantics, and the scoping model, which is nearly everything needed to call it correctly. The remaining gap, the exact personScope UUID form and period format, is already documented in the schema.

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?

Schema coverage is low at 33%, yet the description compensates meaningfully: it explains what forecast mode changes about the output and restates the admin/all scoping that governs personScope. It omits the third option of personScope (a person UUID) and says nothing about the required period format, which the schema pattern already enforces.

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 concrete verb and resource: it returns the monthly distribution of expenses and revenues broken down by category, payment method, and condition. That is specific enough for an agent to know exactly what data it produces, but it never contrasts itself with adjacent tools such as get_category_trends or get_dashboard_overview, so sibling selection still requires inference.

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?

Usage is only implied: the description makes clear this is a monthly aggregate and that scope is either admin or all people, which hints at when to reach for it. It never states when not to use it, nor points to the trend/dashboard siblings that overlap, leaving the agent to guess between them.

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