Skip to main content
Glama
evan-moon

firma

by evan-moon
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

add_flow

Upsert income and expense entries using predefined categories. Supports single entries or bulk imports, grouping results by period.

Instructions

Upsert one or more cash flow entries (also edits — same composite key overwrites). entries is an array: pass one entry to record a single flow item, many to import an income/expense spreadsheet (rows = months, columns = categories) in one call. Prefer add_monthly for full month-end settlement. VALID FLOW CATEGORIES — income (sub_type=employment): salary, business. Income (sub_type=investment): dividends, interest. Income (sub_type=other): income_other. Expense (sub_type=consumption): personal. Expense (sub_type=fixed): insurance, phone, utilities. Expense (sub_type=housing): rent, maintenance. Expense (sub_type=debt): loan_repayment. Expense (sub_type=other): expense_other. Use ONLY these category strings — do NOT invent your own.

A single-entry call returns the upserted entry; a multi-entry call returns counts grouped by period.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entriesYesOne or more flow entries to upsert

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed10 schema fields changedv0.20.0
    • removedInput schema / properties / amount
      Removed value: -{
-  "description": "Amount in `currency` units (whole units)",
-  "type": "integer"
-}
    • removedInput schema / properties / category
      Removed value: -{
-  "description": "Must be one of the predefined flow categories. Income: salary, business, dividends, interest, income_other. Expense: personal, insurance, phone, utilities, rent, maintenance, loan_repayment, expense_other.",
-  "type": "string"
-}
    • removedInput schema / properties / currency
      Removed value: -{
-  "default": "USD",
-  "description": "Currency of `amount` (USD/KRW/JPY/EUR/CNY/GBP). Non-USD converted via historical FX at `date`.",
-  "type": "string"
-}
    • removedInput schema / properties / date
      Removed value: -{
-  "description": "YYYY-MM-DD (typically month-end)",
-  "type": "string"
-}
    • addedInput schema / properties / entries
      Added value: +{
+  "description": "One or more flow entries to upsert",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "amount": {
+        "description": "Amount in `currency` units (whole units)",
+        "type": "integer"
+      },
+      "category": {
+        "description": "Must be one of the predefined flow categories. Income: salary, business, dividends, interest, income_other. Expense: personal, insurance, phone, utilities, rent, maintenance, loan_repayment, expense_other.",
+        "type": "string"
+      },
+      "currency": {
+        "default": "USD",
+        "description": "Currency of `amount` (USD/KRW/JPY/EUR/CNY/GBP/HKD/INR/TWD). Non-USD converted via historical FX at `date`.",
+        "type": "string"
+      },
+      "date": {
+        "description": "YYYY-MM-DD (typically month-end)",
+        "type": "string"
+      },
+      "memo": {
+        "type": "string"
+      },
+      "period": {
+        "description": "YYYY-MM",
+        "type": "string"
+      },
+      "sub_type": {
+        "description": "Must match the category sub_type. Income: employment, investment, other. Expense: consumption, fixed, housing, debt, other.",
+        "type": "string"
+      },
+      "type": {
+        "enum": [
+          "income",
+          "expense"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "period",
+      "date",
+      "type",
+      "sub_type",
+      "category",
+      "amount"
+    ],
+    "type": "object"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • removedInput schema / properties / memo
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / period
      Removed value: -{
-  "description": "YYYY-MM",
-  "type": "string"
-}
    • removedInput schema / properties / sub_type
      Removed value: -{
-  "description": "Must match the category sub_type. Income: employment, investment, other. Expense: consumption, fixed, housing, debt, other.",
-  "type": "string"
-}
    • removedInput schema / properties / type
      Removed value: -{
-  "enum": [
-    "income",
-    "expense"
-  ],
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "period",
-  "date",
-  "type",
-  "sub_type",
-  "category",
-  "amount"
-]New value: +[
+  "entries"
+]
  2. Changed4 schema fields changedv0.1.3
    • changedInput schema / properties / amount / description
      Previous value: -"Amount in USD (whole dollars)"New value: +"Amount in `currency` units (whole units)"
    • addedInput schema / properties / category / description
      Added value: +"Must be one of the predefined flow categories. Income: salary, business, dividends, interest, income_other. Expense: personal, insurance, phone, utilities, rent, maintenance, loan_repayment, expense_other."
    • addedInput schema / properties / currency
      Added value: +{
+  "default": "USD",
+  "description": "Currency of `amount` (USD/KRW/JPY/EUR/CNY/GBP). Non-USD converted via historical FX at `date`.",
+  "type": "string"
+}
    • addedInput schema / properties / sub_type / description
      Added value: +"Must match the category sub_type. Income: employment, investment, other. Expense: consumption, fixed, housing, debt, other."
  3. Changed4 schema fields changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / amount / description
      Previous value: -"Amount in KRW"New value: +"Amount in USD (whole dollars)"
    • removedInput schema / properties / amount / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / amount / minimum
      Removed value: --9007199254740991
  4. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Given no annotations, the description discloses that it performs upserts (overwrites on same key), describes single vs multi-entry return behavior, but does not cover authorization or rate limits.

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?

The description is front-loaded with the core purpose and usage, but the long list of categories, while necessary, adds length. Still efficient overall.

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

Completeness5/5

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

Despite no output schema, the description covers return behavior (single vs multi-entry), upsert semantics, and category constraints, making it complete for the tool's complexity.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant value by explaining that entries can be one or many for spreadsheet-like import, listing valid categories, and describing return values.

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

Purpose5/5

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

The description clearly states the tool upserts cash flow entries and mentions that the same composite key overwrites, which distinguishes it from siblings like add_balance and add_monthly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly advises to prefer add_monthly for full month-end settlement and warns to use only predefined categories, providing clear alternative and constraint.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/evan-moon/firma'

If you have feedback or need assistance with the MCP directory API, please join our Discord server