Skip to main content
Glama
Sign In
OpenMonetis MCP

OpenMonetis MCP

by Welington98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Anexos da transação

list_transaction_attachments
Read-onlyIdempotent

Lists receipts, invoices, and other attachments linked to a transaction ID, helping you review the supporting documents for a financial record.

Instructions

Lista os anexos (comprovantes, notas) vinculados a uma transação.

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": {
      "transactionId": "<transactionId>"
    },
    "name": "list_transaction_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
transactionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.2/5.0
Behavior3/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 the safety profile is fully covered without the description. The description adds little beyond clarifying that attachments are of transaction-receipt/note kinds; it says nothing about empty results, ordering, pagination, or behavior when the transaction has no attachments or does not exist.

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 short sentence with the resource and scope front-loaded; no filler or repetition. It is borderline terse rather than verbose, which is a completeness issue rather than a conciseness one.

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?

This is a simple read tool with one required parameter and full annotation coverage, so not much is required. However, with no output schema the description could reasonably state what is returned (list shape, emptiness, ordering) and how it differs from 'list_attachments', which it omits.

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% for the single transactionId parameter, so the description must carry meaning. It does indicate the parameter selects the transaction whose attachments are returned, but adds no format, validity, or error-handling detail beyond the UUID pattern already encoded in the 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 plus resource ('Lista os anexos') and scopes it to those 'vinculados a uma transação', with parenthetical examples of the attachment types (comprovantes, notas). It does not distinguish itself from the sibling 'list_attachments', leaving ambiguity about which list tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no prerequisites, and no mention of the closely named alternative 'list_attachments'. The agent must infer usage purely from the tool name and the phrase 'vinculados a uma transação'.

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