Skip to main content
Glama

Dayze — Life Context

by com.dayze
OverviewDiscussionsAdmin

Expense Summary

get_expenses
Read-only

Authenticated user cashflow summary: spend, income, net, and top spend categories. Requires OAuth or a supported scoped credential. ($0.10; API key required)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodNoSummary window. Default month.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
netNo
usdNoTotals converted to USD (approximate FX).
countNo
spendNo
incomeNo
periodYes
currencyNo
by_currencyNo
period_daysNo
multi_currencyNo
top_categoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / period
      Added value: +{
+  "description": "Summary window. Default month.",
+  "enum": [
+    "month",
+    "year"
+  ],
+  "type": "string"
+}
  2. Changed3 schema fields changed
    • addedOutput schema / properties / by_currency
      Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "description": "Per-currency spend/income/net — never FX-converted.",
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / multi_currency
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / usd
      Added value: +{
+  "additionalProperties": true,
+  "description": "Totals converted to USD (approximate FX).",
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "currency": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "income": {
+      "type": "number"
+    },
+    "net": {
+      "type": "number"
+    },
+    "period": {
+      "enum": [
+        "month",
+        "year"
+      ],
+      "type": "string"
+    },
+    "period_days": {
+      "type": "number"
+    },
+    "spend": {
+      "type": "number"
+    },
+    "top_categories": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "period"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered by structured data. The description adds genuinely new context: the credential requirement and the $0.10 cost. It doesn't disclose pagination, default period, or result ordering, so it stops short of 5.

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?

Two terse sentences, front-loaded with the resource and its output contents, followed by the auth/cost constraint. No filler, no repetition of the title.

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 single-parameter, read-only summary tool with an output schema (so return values need no explanation), the description covers what is returned, auth, and cost. Only the period default/behavior at the tool level is left implicit, which the schema mostly handles.

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

Parameters3/5

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

Schema description coverage is 100% for the single 'period' parameter (enum month/year, default month documented in schema), so the description cannot and need not add much. Baseline 3 is appropriate; nothing in the description clarifies the parameter beyond the schema.

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?

Names a specific verb+resource ('cashflow summary') and enumerates the content it returns: spend, income, net, top spend categories. This clearly distinguishes it from sibling reads like get_transactions, get_money_between_people, and get_inventory_valuations. However it doesn't explicitly name which sibling to prefer, so it falls 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 Guidelines2/5

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

States the auth prerequisite ('Requires OAuth or a supported scoped credential') but gives no when-to-use vs when-not guidance relative to alternatives such as get_transactions or search_transactions. An agent must infer the aggregation-vs-raw-records distinction on its own.

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

All Dayze — Life Context toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources