Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_status

Read-only

Checks MoneyWiz connectivity and returns the open ledger with current totals.

Instructions

Check the connection to MoneyWiz and report the open ledger and totals.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds that output includes the open ledger and totals, which is genuinely useful given there is no output schema, but it says nothing about failure behavior (throw vs. return a status) or latency/auth requirements.

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 short sentence with the action and the returned data front-loaded; nothing is padded or redundant.

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 zero-param read-only tool this is close to complete, but 'totals' is undefined (account balances? net worth? per-ledger?) and with no output schema the agent cannot resolve that from elsewhere. The absence of any statement about what happens on a failed connection is a further gap for a diagnostic tool.

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 nothing for the description to disambiguate and the baseline of 4 applies. No parameter meaning is lost or misleading.

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 gives a concrete verb ('Check') plus resource ('the connection to MoneyWiz') and adds what is reported back ('the open ledger and totals'). That is enough to separate it from the surrounding CRUD siblings, though it never explicitly names itself as the sole diagnostic tool.

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?

When-to-use is only implied by the words 'Check the connection'; there is no explicit statement like 'call this before other operations' or 'use this when a request fails'. No alternatives or exclusions are named, so the agent must infer the diagnostic role.

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