Skip to main content
Glama

Dayze — Life Context

Log Income

log_income

Record money received (Stripe, refunds, payroll, Venmo). log_transaction with type income and direction from already set (pass neither). Use external_id for Stripe/Gmail idempotency. A contact paying back an IOU: category "IOU repayment" + person_id (lowers the IOU, shows the money once). A contact lending the user cash: category "IOU lend" + person_id (creates the IOU the user owes, shows the money once). ($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>"
    },
    "name": "log_income"
  }
}

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.
notesNoFree text about the payment. Alias: description.
amountYesPositive money amount in the stated currency, e.g. 12.50.
sourceNoPayment rail or app, e.g. stripe.
projectNoProject label stored as project:{slug} tag, e.g. Max Soko poker venture.
categoryNoe.g. Salary, Gift, Refund. "IOU repayment" and "IOU lend" need person_id.
currencyNoISO 4217 currency 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, e.g. Blue Bottle.
timezoneNoIANA timezone or ±HH:MM; required for an exact instant with date+time.
person_idNoContact id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
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.
request_idNoClient idempotency key (retries return original result).
descriptionNoAlias for notes.
external_idNoProvider id that dedupes imports, e.g. venmo-gmail-18c2a1b.
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.
payment_methodNoHow it was paid, e.g. card.
time_certaintyNoexact, inferred, or unknown. Default exact when time/occurred_at is set.
idempotency_keyNoAlias for request_id.
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. Changed17 schema fields changed
    • addedInput schema / properties / amount / description
      Added value: +"Positive money amount in the stated currency, e.g. 12.50."
    • 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."
    • addedInput schema / properties / currency / description
      Added value: +"ISO 4217 currency 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 / external_id / description
      Added value: +"Provider id that dedupes imports, e.g. venmo-gmail-18c2a1b."
    • 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, e.g. Blue Bottle."
    • 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: +"How it was paid, e.g. card."
    • addedInput schema / properties / person_id / description
      Added value: +"Contact id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809."
    • 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 or app, e.g. stripe."
    • 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."
  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. Changed3 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."
    • 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. Changed6 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"
      +}
    • 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"
      +}
  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: -"e.g. Salary, Gift, Refund. \"IOU repayment\" needs person_id."New value: +"e.g. Salary, Gift, Refund. \"IOU repayment\" and \"IOU lend\" need person_id."
  8. Changed2 schema fields changed
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "e.g. Salary, Gift, Refund. \"IOU repayment\" 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. Changed1 schema field changed
    • addedOutput schema / properties / event_id
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  10. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare it as a non-read-only, non-destructive, closed-world write; the description adds cost ($0.10), the API-key requirement, idempotency behavior via external_id and request_id, and the side effects of the IOU categories ('lowers the IOU', 'creates the IOU the user owes', 'shows the money once'). It stops short of describing failure modes or how a duplicate import is reported, but the added behavioral context is well beyond the annotations.

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?

Four sentences, front-loaded with the core purpose, then the alternative, then the two IOU edge cases, then operational constraints in parentheses. It is telegraphic in places ('pass neither', 'lowers the IOU, shows the money once') but nearly every clause carries actionable information; only the trailing cost/auth parenthetical feels tacked on.

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?

For a 24-parameter write tool with an output schema and annotations, the description covers the highest-risk ambiguities: sibling routing, IOU category semantics, and idempotency. It does not explain currency/date defaults or how amounts are validated, but the schema documents those and the output schema handles return values, so nothing critical is missing.

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?

Schema coverage is already 100%, so the baseline would be 3; the description still adds meaning by tying category, person_id, and cash_moved together into a decision rule rather than leaving them as independent fields. The external_id-as-idempotency-key hint and the explicit 'pass neither' instruction for type/direction are guidance the schema alone does not convey.

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?

States a specific verb and resource ('Record money received') and immediately enumerates the sources it covers (Stripe, refunds, payroll, Venmo). It also distinguishes itself from the closest sibling by stating the equivalent call is log_transaction with type income and direction from already set, so an agent can pick between them without opening either schema.

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

Usage Guidelines5/5

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

Explicit routing is given: use log_transaction with fixed type/direction instead, pass neither here. It also gives concrete conditional rules for ambiguous cases — a contact repaying an IOU uses category "IOU repayment" with person_id, a contact lending cash uses "IOU lend" with person_id, and not_iou_repayment exists for unrelated contact income — which is exactly the when/when-not guidance an agent needs.

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.