Skip to main content
Glama
Sign In
OpenMonetis MCP

OpenMonetis MCP

by Welington98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Parcelamentos

list_installments
Read-onlyIdempotent

Lists a user's installment plans for a given month, showing open or completed series, paid and pending installments, amounts, and progress.

Instructions

Lista as séries parceladas do usuário no mês: séries abertas/concluídas, parcelas pagas e pendentes, valores e progresso. As séries vêm em versão compacta por padrão; use detail: "full" para o objeto completo.

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

Input Schema

NameRequiredDescriptionDefault
qNo
detailNocompact devolve as séries essenciais; full devolve o objeto completo da API.compact
periodYes
statusNoopen

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description adds that results come back in a compact shape by default, which is useful behavioral context, but says nothing about result volume, ordering, or whether the month must be a closed period – the compact default is also largely echoed in the schema's `detail` description.

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?

Two sentences, front-loaded with what is listed and then the compact-by-default behavior; nothing is padding. The second sentence partly duplicates the schema's own `detail` wording, which is the only redundancy.

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 read-only list tool with no output schema, describing the returned contents in the first sentence is the right move. However, with four parameters at low schema coverage and no output schema, the definition should still clarify the `period` format, what `q` filters, and the `status` default – none of which is addressed.

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 only 25%, so the description must carry more weight. It explains `detail` (compact vs full) and implies `period` is a month, but leaves `q` completely unexplained and only hints at `status` through the words 'abertas/concluídas' without tying them to the enum or noting that sharing between the two happens. Partial compensation only.

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?

A specific verb + resource is stated: listing the user's installment series for a month, and it further enumerates what each series contains (open/completed series, paid and pending installments, values, progress). It does not name or distinguish itself from siblings like `anticipate_installments` or `quote_installments`.

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 by the month scoping ("no mês"), and the `detail: "full"` hint gives a concrete call pattern when the compact form is insufficient. There is no explicit when-to-use/when-not-to-use guidance versus the installment siblings, which is the main gap.

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