Skip to main content
Glama
Sign In
OpenMonetis MCP

OpenMonetis MCP

by Welington98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Detalhar transação

get_transaction
Read-onlyIdempotent

Retrieve complete transaction details by ID, including amounts, splits, card/account, category, due date, installments, recurrence, refunds, and attachments.

Instructions

Retorna todos os campos de uma transação: valores, rateio entre pessoas, cartão/conta, categoria, vencimento, parcelas, recorrência, reembolsos e anexos.

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": {
      "id": "<id>"
    },
    "name": "get_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID da transação.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.7/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 safety is covered. The description adds value the annotations cannot: it discloses the breadth of the returned payload (split between people, card/account, category, due date, installments, recurrence, refunds, attachments), with no output schema to convey this otherwise.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the field enumeration is the substance rather than padding. It is slightly long-tailed but every listed item conveys return shape.

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 correctly substitutes a payload summary, and annotations cover the read-only/idempotent profile. It omits error behavior for an unknown or malformed id and whether attachment entries are full content or metadata, which are minor for a detail-fetch tool.

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?

Only one parameter (id) exists with 100% schema description coverage, so the schema already fully documents it. The description adds no further meaning about the identifier format or what happens when the id does not exist, which is the correct baseline for a fully documented single-param schema.

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 uses a specific verb ('Retorna') with a specific resource ('uma transação', singular) and enumerates the fields returned, which separates it from list/update/delete siblings. It does not name a sibling explicitly, so differentiation is inferred rather than stated.

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 implied: fetch the full record for one known transaction id. There is no explicit 'use this when' or 'prefer X instead' guidance, and no mention of how it relates to the transaction list or update tools, but the singular resource makes the intent clear enough to act on.

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