Skip to main content
Glama
Sign In
OpenMonetis MCP

OpenMonetis MCP

by Welington98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Listar orçamentos

list_budgets
Read-onlyIdempotent

Lists monthly budgets by category, showing planned, spent, remaining amounts and usage percentage for a given YYYY-MM period.

Instructions

Lista os orçamentos de um mês por categoria, com valor planejado, gasto, restante e percentual de uso.

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

Input Schema

NameRequiredDescriptionDefault
periodYesMês de referência no formato YYYY-MM.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.5/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 by structured data. The description adds genuinely new value by disclosing the returned fields (planejado, gasto, restante, percentual de uso), which matters because there is no output schema, but it says nothing about ordering, pagination, or behavior when no budgets exist for the month.

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 well-formed sentence that front-loads the action and resource before the returned fields; no filler or redundant restatement of the title. It is efficient, if a bit terse for a tool whose output shape is otherwise undocumented.

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?

For a one-parameter, read-only list tool with full annotation coverage and a fully documented schema, the description supplies the missing piece: what the result contains, which substitutes for the absent output schema. Only secondary details (ordering, empty-month behavior, currency) are omitted.

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?

There is only one parameter and schema description coverage is 100%, with a regex already enforcing YYYY-MM, so the baseline is 3. The phrase 'de um mês' confirms that the period is a single reference month rather than a date range, which slightly reinforces the schema without adding format or edge-case guidance.

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 names a specific verb and resource ('Lista os orçamentos') and adds scope ('de um mês por categoria') plus the returned metrics. An agent can immediately tell this reads budget data rather than mutating it, though nothing explicitly distinguishes it from create_budget or from other list_* siblings.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative. Usage is only implied by the verb 'Lista' and the month scope, which a competent agent can infer but which is not spelled out.

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