Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Resumo financeiro da pessoa

get_person_summary
Read-onlyIdempotent

Retrieves a person's monthly financial summary, including total expenses, transaction history, and category distribution, to help analyze spending by person and period.

Instructions

Retorna o resumo financeiro de uma pessoa em um mês: total de despesas, histórico e distribuição por categoria.

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

Input Schema

NameRequiredDescriptionDefault
periodYes
personIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish that this is a safe, read-only, idempotent operation, and the description adds monthly scope and the three included result components. It does not clarify what "histórico" contains, whether the period means a calendar month, or how a person/month without activity is handled.

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?

The single sentence is front-loaded with the operation and scope, then efficiently enumerates the returned components. There is no redundant or promotional wording.

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 simple two-parameter read, the description and constrained schema are sufficient for basic invocation. However, with no output schema, the ambiguous "histórico" component and lack of differentiation from nearby person-level financial tools leave meaningful selection and result-interpretation gaps.

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?

Despite 0% schema description coverage, the description supplies the essential semantics: the person is the summary subject and the period selects a month. It only implicitly maps these ideas to personId and period and adds no guidance about obtaining the UUID or whether any month within the valid YYYY-MM format is acceptable.

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 clearly states the verb, resource, and scope: it returns one person's financial summary for a month. Listing total expenses, history, and category distribution clarifies the result, although it does not explicitly distinguish this tool from get_person_balance or get_person_report.

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?

Monthly financial review is an implied use case, and the listed components help an agent recognize when the tool is relevant. There is no explicit guidance about when to prefer it over a balance, report, dashboard, or distribution tool, nor any exclusions or prerequisites.

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