Skip to main content
Glama
Sign In
OpenMonetis MCP

OpenMonetis MCP

by Welington98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Configurações do usuário

get_settings
Read-onlyIdempotent

Fetches account transaction defaults, dashboard preferences, and security settings in one call so agents can review configuration before making changes.

Instructions

Retorna as preferências da conta (defaults de transação, preferências do dashboard) e as configurações de segurança, em uma única chamada.

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": "get_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds useful scope context by naming the two setting categories returned, but it says nothing about sensitivity handling (e.g. whether security settings are masked), per-user scoping, or the shape of the response.

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

Conciseness5/5

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

A single sentence with zero waste, front-loaded with the verb and the primary resource, followed by the enumerated contents and the consolidation note. Nothing could be removed without losing information.

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 input parameters, no output schema and full annotation coverage, the description needs only to say what is returned, which it does. The only minor gaps are the response shape and whether security values are redacted, which are not strictly required for an agent to call a parameterless getter correctly.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to supply; the baseline for a parameterless tool applies. The description correctly implies no filtering or selection input is needed.

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 states a specific verb ("Retorna") and resource ("preferências da conta" plus "configurações de segurança") and enumerates the content: transaction defaults and dashboard preferences. It is clear what the tool returns, but it does not differentiate itself from nearby read tools such as get_account or get_dashboard_overview, so it stops short of a 5.

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?

The phrase "em uma única chamada" implies this is the consolidated way to fetch preferences and security settings rather than making several calls, which is implicit usage guidance. However, there is no explicit when-to-use or when-not-to-use statement and no named alternative, leaving routing to inference.

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