Skip to main content
Glama

Dayze — Life Context

Log Transaction

log_transaction

Income/expense/transfer. from+income = received. IOU repayment/lend need category + person_id (direction from/to). Invoice: iou_type invoice. Open-IOU income needs not_iou_repayment=true. Unknown person_id errors; changes nothing. ($0.10; API key required)

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": {
      "amount": "<amount>",
      "direction": "<direction>"
    },
    "name": "log_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD; default today. Prefer with time + timezone when the source has a clock time.
tagsNoOptional tags. Prefer project: / ext: / rail: grammar.
timeNoHH:mm or HH:mm:ss; no default. Pair with timezone or occurred_at.
typeNoTransaction type.
notesNoFree text about the payment. Alias: description.
amountYesPositive money amount.
sourceNoPayment rail, e.g. venmo.
projectNoProject label stored as project:{slug} tag, e.g. Max Soko poker venture.
categoryNoLedger category (e.g. Salary, Gift, Food & Dining). "IOU repayment" / "IOU lend" / "Invoice payment" need person_id.
currencyNoISO 4217 code, e.g. USD.
iou_typeNoloan (default) or invoice. Invoice = unpaid receivable (no Finance outflow); payment is income "Invoice payment". "I lent…" → loan.
merchantNoMerchant or payee name.
timezoneNoIANA timezone or ±HH:MM; required for an exact instant with date+time.
directionYesfrom = received, to = paid.
person_idNoOwned contact id; required for IOU categories. Unknown/other-user id errors and changes nothing.
account_idNoStable provider account identity for imported payments.
cash_movedNoWith category "IOU lend": true (default) = cash changed hands as a loan (Finance); false = an owed share (IOU only). Ignored for iou_type invoice.
message_idNoSource Gmail message id.
request_idNoClient idempotency key (retries return original result).
descriptionNoAlias for notes.
external_idNoProvider id; dedupes imports.
occurred_atNoOffset-aware ISO timestamp from the source. Never use ingestion/created_at.
person_nameNoContact by name when there is no person_id (IOU categories need one).
client_labelNoOptional free-text client label for an invoice IOU.
mirror_eventNoAlso insert optional Money calendar event (default false)
payment_methodNoAlias for source.
time_certaintyNoexact, inferred, or unknown. Default exact when time/occurred_at is set.
idempotency_keyNoAlias for request_id.
extractor_versionNoExtractor/parser version for imports.
not_iou_repaymentNotrue only when income from a contact with an open IOU is unrelated to it.

Output Schema

NameRequiredDescriptionDefault
typeNo
accountNoThe Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
messageNo
event_idNo
directionNo
duplicateNo
expense_idNo
provenanceNoWhich connector wrote the record and which connected Dayze account received it.
inspect_urlNoThe Dayze page that shows the saved record.
transactionNoExpense/income transaction row.
inspect_noteNoWhat inspect_url opens. Never quote the record id.
transaction_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed23 schema fields changed
    • addedInput schema / properties / amount / description
      Added value: +"Positive money amount."
    • changedInput schema / properties / cash_moved / description
      Previous value: -"With category \"IOU lend\": true (default) = cash changed hands as a loan (shows in Finance); false = an owed share, e.g. of a dinner logged as its own expense (IOU only). Ignored for iou_type invoice."New value: +"With category \"IOU lend\": true (default) = cash changed hands as a loan (Finance); false = an owed share (IOU only). Ignored for iou_type invoice."
    • changedInput schema / properties / category / description
      Previous value: -"Ledger category (e.g. Salary, Gift, Refund, Transfer in, Food & Dining). \"IOU repayment\" = a contact paying back a loan IOU; \"IOU lend\" = a cash loan; \"Invoice payment\" = collecting an unpaid invoice (need person_id)."New value: +"Ledger category (e.g. Salary, Gift, Food & Dining). \"IOU repayment\" / \"IOU lend\" / \"Invoice payment\" need person_id."
    • addedInput schema / properties / currency / description
      Added value: +"ISO 4217 code, e.g. USD."
    • changedInput schema / properties / date / description
      Previous value: -"YYYY-MM-DD civil transaction date; default today. Prefer with time + timezone when the source has a clock time (e.g. Zelle SMS)."New value: +"YYYY-MM-DD; default today. Prefer with time + timezone when the source has a clock time."
    • addedInput schema / properties / direction / description
      Added value: +"from = received, to = paid."
    • addedInput schema / properties / external_id / description
      Added value: +"Provider id; dedupes imports."
    • addedInput schema / properties / extractor_version / description
      Added value: +"Extractor/parser version for imports."
    • changedInput schema / properties / iou_type / description
      Previous value: -"loan (default) or invoice. Invoice = unpaid receivable: no Finance outflow on create; payment is income \"Invoice payment\". Use for invoice/receivable phrasings; \"I lent…\" → loan."New value: +"loan (default) or invoice. Invoice = unpaid receivable (no Finance outflow); payment is income \"Invoice payment\". \"I lent…\" → loan."
    • addedInput schema / properties / merchant / description
      Added value: +"Merchant or payee name."
    • addedInput schema / properties / message_id / description
      Added value: +"Source Gmail message id."
    • changedInput schema / properties / mirror_event / description
      Previous value: -"Also insert optional Money · calendar event (default false)"New value: +"Also insert optional Money calendar event (default false)"
    • changedInput schema / properties / occurred_at / description
      Previous value: -"Offset-aware ISO timestamp for the transaction (…Z or ±HH:MM). Preferred when the source has one. Never use ingestion/created_at."New value: +"Offset-aware ISO timestamp from the source. Never use ingestion/created_at."
    • addedInput schema / properties / payment_method / description
      Added value: +"Alias for source."
    • addedInput schema / properties / person_id / description
      Added value: +"Owned contact id; required for IOU categories. Unknown/other-user id errors and changes nothing."
    • changedInput schema / properties / person_name / description
      Previous value: -"The contact by name, when there is no person_id (IOU categories need one or the other)."New value: +"Contact by name when there is no person_id (IOU categories need one)."
    • changedInput schema / properties / project / description
      Previous value: -"Venture/project label → stored as project:{slug} tag (e.g. Max Soko poker venture)"New value: +"Project label stored as project:{slug} tag, e.g. Max Soko poker venture."
    • addedInput schema / properties / source / description
      Added value: +"Payment rail, e.g. venmo."
    • addedInput schema / properties / tags / items / description
      Added value: +"Tag, e.g. work."
    • changedInput schema / properties / time / description
      Previous value: -"HH:mm or HH:mm:ss source wall-clock transaction time. Does not default to now. Pair with timezone (or pass occurred_at)."New value: +"HH:mm or HH:mm:ss; no default. Pair with timezone or occurred_at."
    • changedInput schema / properties / time_certainty / description
      Previous value: -"exact (source stamp), inferred, or unknown. Default exact when time/occurred_at is supplied."New value: +"exact, inferred, or unknown. Default exact when time/occurred_at is set."
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA timezone (e.g. America/New_York) or explicit ±HH:MM for `time`. Required for an exact instant when using date+time; never silently assumed."New value: +"IANA timezone or ±HH:MM; required for an exact instant with date+time."
    • addedInput schema / properties / type / description
      Added value: +"Transaction type."
  2. Changed5 schema fields changed
    • addedInput schema / properties / date / description
      Added value: +"YYYY-MM-DD civil transaction date; default today. Prefer with time + timezone when the source has a clock time (e.g. Zelle SMS)."
    • addedInput schema / properties / occurred_at
      Added value: +{
      +  "description": "Offset-aware ISO timestamp for the transaction (…Z or ±HH:MM). Preferred when the source has one. Never use ingestion/created_at.",
      +  "type": "string"
      +}
    • addedInput schema / properties / time
      Added value: +{
      +  "description": "HH:mm or HH:mm:ss source wall-clock transaction time. Does not default to now. Pair with timezone (or pass occurred_at).",
      +  "type": "string"
      +}
    • addedInput schema / properties / time_certainty
      Added value: +{
      +  "description": "exact (source stamp), inferred, or unknown. Default exact when time/occurred_at is supplied.",
      +  "type": "string"
      +}
    • addedInput schema / properties / timezone
      Added value: +{
      +  "description": "IANA timezone (e.g. America/New_York) or explicit ±HH:MM for `time`. Required for an exact instant when using date+time; never silently assumed.",
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • addedOutput schema / properties / inspect_note
      Added value: +{
      +  "description": "What inspect_url opens. Never quote the record id.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / inspect_url
      Added value: +{
      +  "description": "The Dayze page that shows the saved record.",
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • addedOutput schema / properties / account
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.",
      +  "properties": {
      +    "display_name": {
      +      "description": "Account display name.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "handle": {
      +      "description": "Account handle, e.g. @goh.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "note": {
      +      "description": "How to disclose the account to the user.",
      +      "type": "string"
      +    },
      +    "qa_fixture": {
      +      "description": "True for a known QA test account: its records are fixture data, not a real life.",
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "handle",
      +    "display_name",
      +    "qa_fixture",
      +    "note"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / provenance
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Which connector wrote the record and which connected Dayze account received it.",
      +  "properties": {
      +    "account": {
      +      "additionalProperties": false,
      +      "description": "The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.",
      +      "properties": {
      +        "display_name": {
      +          "description": "Account display name.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "handle": {
      +          "description": "Account handle, e.g. @goh.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "note": {
      +          "description": "How to disclose the account to the user.",
      +          "type": "string"
      +        },
      +        "qa_fixture": {
      +          "description": "True for a known QA test account: its records are fixture data, not a real life.",
      +          "type": "boolean"
      +        }
      +      },
      +      "required": [
      +        "handle",
      +        "display_name",
      +        "qa_fixture",
      +        "note"
      +      ],
      +      "type": "object"
      +    },
      +    "channel": {
      +      "description": "Always mcp_connector.",
      +      "type": "string"
      +    },
      +    "connector": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "kind": {
      +          "description": "oauth or api_key.",
      +          "type": "string"
      +        },
      +        "name": {
      +          "description": "The connected app or API-key label shown to the account owner.",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "kind",
      +        "name"
      +      ],
      +      "type": "object"
      +    },
      +    "source": {
      +      "description": "chatgpt for ChatGPT OAuth writes; mcp for another OAuth app or API key.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "source",
      +    "channel",
      +    "connector",
      +    "account"
      +  ],
      +  "type": "object"
      +}
  5. Changed4 schema fields changed
    • changedInput schema / properties / cash_moved / description
      Previous value: -"With category \"IOU lend\": true (default) = cash changed hands as a loan (shows in Finance); false = an owed share, e.g. of a dinner logged as its own expense (IOU only)."New value: +"With category \"IOU lend\": true (default) = cash changed hands as a loan (shows in Finance); false = an owed share, e.g. of a dinner logged as its own expense (IOU only). Ignored for iou_type invoice."
    • changedInput schema / properties / category / description
      Previous value: -"Ledger category (e.g. Salary, Gift, Refund, Transfer in, Food & Dining). \"IOU repayment\" = a contact paying back an IOU; \"IOU lend\" = a cash loan to or from a contact (both need person_id)."New value: +"Ledger category (e.g. Salary, Gift, Refund, Transfer in, Food & Dining). \"IOU repayment\" = a contact paying back a loan IOU; \"IOU lend\" = a cash loan; \"Invoice payment\" = collecting an unpaid invoice (need person_id)."
    • addedInput schema / properties / client_label
      Added value: +{
      +  "description": "Optional free-text client label for an invoice IOU.",
      +  "type": "string"
      +}
    • addedInput schema / properties / iou_type
      Added value: +{
      +  "description": "loan (default) or invoice. Invoice = unpaid receivable: no Finance outflow on create; payment is income \"Invoice payment\". Use for invoice/receivable phrasings; \"I lent…\" → loan.",
      +  "type": "string"
      +}
  6. Changed4 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "Alias for notes.",
      +  "type": "string"
      +}
    • addedInput schema / properties / notes / description
      Added value: +"Free text about the payment. Alias: description."
    • addedInput schema / properties / person_name
      Added value: +{
      +  "description": "The contact by name, when there is no person_id (IOU categories need one or the other).",
      +  "type": "string"
      +}
  7. Changed2 schema fields changed
    • addedInput schema / properties / cash_moved
      Added value: +{
      +  "description": "With category \"IOU lend\": true (default) = cash changed hands as a loan (shows in Finance); false = an owed share, e.g. of a dinner logged as its own expense (IOU only).",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / category / description
      Previous value: -"Ledger category (e.g. Salary, Gift, Refund, Transfer in, Food & Dining). \"IOU repayment\" = a contact paying back an IOU (needs person_id)."New value: +"Ledger category (e.g. Salary, Gift, Refund, Transfer in, Food & Dining). \"IOU repayment\" = a contact paying back an IOU; \"IOU lend\" = a cash loan to or from a contact (both need person_id)."
  8. Changed2 schema fields changed
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "Ledger category (e.g. Salary, Gift, Refund, Transfer in, Food & Dining). \"IOU repayment\" = a contact paying back an IOU (needs person_id).",
      +  "type": "string"
      +}
    • addedInput schema / properties / not_iou_repayment
      Added value: +{
      +  "description": "true only when income from a contact with an open IOU is unrelated to it.",
      +  "type": "boolean"
      +}
  9. Changed3 schema fields changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Stable provider account identity for imported payments.",
      +  "type": "string"
      +}
    • addedInput schema / properties / extractor_version
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / message_id
      Added value: +{
      +  "type": "string"
      +}
  10. Changed2 schema fields changed
    • addedInput schema / properties / mirror_event
      Added value: +{
      +  "description": "Also insert optional Money · calendar event (default false)",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / event_id
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  11. Changed2 schema fields changed
    • addedInput schema / properties / project
      Added value: +{
      +  "description": "Venture/project label → stored as project:{slug} tag (e.g. Max Soko poker venture)",
      +  "type": "string"
      +}
    • addedInput schema / properties / tags
      Added value: +{
      +  "description": "Optional tags. Prefer project: / ext: / rail: grammar.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  12. Changed1 schema field changed
    • addedInput schema / properties / payment_method
      Added value: +{
      +  "type": "string"
      +}
  13. Changed2 schema fields changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "Alias for request_id.",
      +  "type": "string"
      +}
    • addedInput schema / properties / request_id
      Added value: +{
      +  "description": "Client idempotency key (retries return original result).",
      +  "type": "string"
      +}
  14. Changed3 schema fields changed
    • addedInput schema / properties / merchant
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / notes
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "amount"
      -]New value: +[
      +  "amount",
      +  "direction"
      +]
  15. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, openWorld=false) the description discloses three things annotations cannot: a per-call cost of $0.10, an API-key requirement, and failure atomicity ('Unknown person_id errors; changes nothing'). It does not discuss idempotency/dedupe behavior at the tool level, which keeps it from a 5.

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?

Every fragment carries a rule and there is no filler; cost and auth are compactly appended. The telegraphic style ('IOU repayment/lend need category + person_id') and the leading enum dump rather than a front-loaded statement of purpose cost it a point on readability.

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?

An output schema exists, so return values need no explanation, and the schema itself documents all 30 parameters. Still, for a tool this complex the description omits the transfer case entirely and gives no routing versus the dedicated log_expense/log_income siblings, leaving real gaps for an agent choosing among them.

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?

With 100% schema coverage the baseline is 3, but the description adds cross-field meaning the per-parameter schema does not spell out: 'from+income = received' binds direction to type, and the IOU/invoice/open-IOU rules bind category, person_id, iou_type and not_iou_repayment together. The transfer path is left without any equivalent guidance, so it is strong but not complete.

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 opening 'Income/expense/transfer' enumerates the resource domain and its three modes, which an agent can map to the type enum, so the purpose is recoverable without opening the schema. However, there is no verb phrase ('log a transaction') and no differentiation from the sibling log_expense / log_income tools, 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?

It gives useful conditional routing for sub-cases: IOU repayment/lend need category + person_id, invoice uses iou_type invoice, and open-IOU income needs not_iou_repayment=true. What is absent is any statement of when to call this tool versus log_expense or log_income, or when not to call it at all, so usage is implied rather than prescribed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.