Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Listar contas

list_accounts
Read-onlyIdempotent

Retrieve a user's financial accounts with type, balance, and whether each is excluded from the consolidated balance. Choose compact or full detail; set an optional YYYY-MM reference month.

Instructions

Lista as contas financeiras do usuário com tipo, saldo e indicação de exclusão do saldo consolidado.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNocompact retorna nome, tipo e saldo; full devolve o objeto completo.compact
periodNoMês de referência (YYYY-MM) para os saldos.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety behavior is covered. The description adds value by disclosing what each returned item contains, including a flag for exclusion from the consolidated balance, but says nothing about ordering, pagination, or empty-result behavior. With annotations carrying the safety profile, this is adequate but not rich.

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 or redundancy. It is efficient, though it stops short of adding the routing or return-shape detail that would justify a top score.

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?

This is a simple, zero-required-parameter, read-only list tool with full annotation coverage and full schema description coverage. With no output schema, the description usefully enumerates the returned fields, which is the main gap it needed to fill; only pagination and ordering remain unstated.

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 description coverage is 100%, so both parameters (detail enum and period) are already documented, making the baseline 3. The description's mention of tipo and saldo being returned slightly reinforces the compact/full distinction described in the schema, nudging it above baseline without adding new parameter semantics.

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 specific verb and resource ("Lista as contas financeiras do usuário") and names the fields returned (tipo, saldo, indicação de exclusão do saldo consolidado). It is clearly distinguishable from siblings like list_transactions or list_cards by the resource alone, though it never explicitly contrasts with them.

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 guidance on when to call this versus alternatives (e.g. create_account, or account-related listings), nor any mention of prerequisites or when not to use it. The scope "do usuário" is the only constraint, and it is implied rather than stated as usage direction.

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