Skip to main content
Glama
Sign In
monarch-mcp2-obot

monarch-mcp2-obot

by dcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Cashflow Get Cashflow Summary

cashflow_get_cashflow_summary
Read-onlyIdempotent

Get a cash flow summary for any date range, applying optional filters by accounts, categories, tags, or merchants to analyze income and spending.

Instructions

Get cashflow summary.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "cashflow_get_cashflow_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional dotted output field paths to return, such as ['id', 'merchant.name', 'category.name'].
filtersNo
end_dateYes
start_dateYes
output_modeNoOutput shape to return. Use summary for compact CLI-style defaults, full for complete structured data without raw, and raw for complete structured data including raw payloads.summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already provide the safety profile: readOnlyHint=true, idempotentHint=true, and destructiveHint=false. However, the description itself adds no behavioral insight beyond those annotations; it does not mention date-range semantics, filtering behavior, or what shape of summary is returned.

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

Conciseness2/5

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

The description is extremely short and free of filler, but this is under-specification rather than effective conciseness. It uses none of the available space to clarify scope, inputs, or output.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, five parameters, required date strings, a nested filter object, and several closely related sibling tools, the description is far too minimal to support correct tool selection or invocation. An agent would still not know what data is returned or what date formats are expected.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides zero parameter-level meaning. Schema description coverage is only 40%, so the description needed to compensate for undocumented parameters such as start_date, end_date, and the nested filters object, but it does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a verbatim restatement of the tool name and title: 'Get cashflow summary.' It names a verb and resource but adds no definition of what a cashflow summary actually contains, and it does not differentiate this tool from sibling tools like cashflow_get_cashflow_trends or cashflow_get_cashflow_breakdown.

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 usage context, no when-to-use guidance, and no mention of alternatives. The description only implies the generic action without telling an agent when to select this over the other cashflow tools or reports_get_report_data.

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