Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Relatório mensal da pessoa

get_person_report
Read-onlyIdempotent

Retrieves an external person's monthly expense and reimbursement report with totals and splits for a given period. Use get_person_summary for administrators, who have no report.

Instructions

Retorna o relatório mensal completo de uma pessoa externa em um período: linhas de despesas e reembolsos, totais e rateios — o mesmo conteúdo do PDF enviado por e-mail. O administrador não possui relatório (a API responde 400 nesse caso); para ele use get_person_summary.

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

Input Schema

NameRequiredDescriptionDefault
periodYes
personIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered; the description adds genuinely new behavior: the 400 response for admin users and the equivalence to the emailed PDF. It does not discuss pagination or response shaping, but for an idempotent read that is minor.

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, no filler: the first defines output scope, the second handles the exclusion and the alternative. The constraint that matters most for selection is not buried.

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?

With no output schema, the description still enumerates the returned content (expense/reimbursement lines, totals, rateios) well enough to judge relevance, and the admin exclusion is covered; only the parameter format details are missing.

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 0%, so the description must carry parameter meaning; it conveys conceptually that a person and a period are required but never states the expected period format (YYYY-MM) or that personId is a UUID, leaving the schema patterns as the only source of syntax.

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?

Names a specific verb and resource ('Retorna o relatório mensal completo de uma pessoa externa em um período') and enumerates the payload (linhas de despesas e reembolsos, totais e rateios), which distinguishes it from get_person_summary and get_person_balance.

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?

States the eligibility condition explicitly ('pessoa externa'), warns that the admin case fails with HTTP 400, and routes that case to a named alternative, get_person_summary. Both when-to-use and when-not-to-use are covered with no inference required.

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