haus

create_subscription

Track a bill such as a streaming service or membership, with an optional fee and cron renewal schedule (no more often than daily). A bill with no renewal schedule is a one-off. Set paymentDate only when the money leaves the account on a different day from the renewal.

Input Schema

TableJSON Schema

Name	Required	Description
`fee`	No	Recurring charge.
`name`	Yes	Name, e.g. 'Netflix' or 'Gym membership'.
`notes`	No	Free-text notes.
`status`	Yes	Status at creation.
`remindMe`	No	Whether to remind the household before each renewal.
`startDate`	No	Renewal date, YYYY-MM-DD. Optional. For a recurring bill it is the first renewal; for a one-off it is the date it is due.
`paymentDate`	No	Date the first payment leaves the account, YYYY-MM-DD, when it differs from the renewal date. Payments repeat on the renewal cadence from this date. Omit when payment happens on renewal.
`renewalCronExpression`	No	Cron expression for the renewal cadence. No more often than daily. Omit for a one-off bill.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`title`	No
`message`	No
`variant`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 24, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "fee": {
-      "currencyCode": "USD",
-      "value": 1599
-    },
-    "name": "Netflix",
-    "notes": "Family plan, shared with parents",
-    "remindMe": true,
-    "renewalCronExpression": "0 0 1 * *",
-    "status": "Active"
-  }
-]New value: +[
+  {
+    "fee": {
+      "currencyCode": "USD",
+      "value": 1599
+    },
+    "name": "Netflix",
+    "notes": "Family plan, shared with parents",
+    "paymentDate": "2026-10-03",
+    "remindMe": true,
+    "renewalCronExpression": "0 0 1 * *",
+    "startDate": "2026-10-01",
+    "status": "Active"
+  }
+]

addedInput schema / properties / paymentDate

Added value: +{
+  "description": "Date the first payment leaves the account, YYYY-MM-DD, when it differs from the renewal date. Payments repeat on the renewal cadence from this date. Omit when payment happens on renewal.",
+  "examples": [
+    "2026-10-03"
+  ],
+  "type": "string"
+}

changedInput schema / properties / renewalCronExpression / description

Previous value: -"Cron expression for the renewal cadence. No more often than daily."New value: +"Cron expression for the renewal cadence. No more often than daily. Omit for a one-off bill."

addedInput schema / properties / startDate

Added value: +{
+  "description": "Renewal date, YYYY-MM-DD. Optional. For a recurring bill it is the first renewal; for a one-off it is the date it is due.",
+  "examples": [
+    "2026-10-01"
+  ],
+  "type": "string"
+}

Changed3 schema fields changedSep 18, 2026

changedInput schema / properties / fee / properties / currencyCode / description

Previous value: -"ISO 4217 code, three letters."New value: +"Uppercase ISO 4217 code, e.g. USD, GBP, JPY."

addedInput schema / properties / fee / properties / currencyCode / pattern
```
Added value: +"^[A-Z]{3}$"
```

changedInput schema / properties / fee / properties / value / description

Previous value: -"Amount in minor units, e.g. cents."New value: +"Amount in the currency's minor units. Most currencies have 2 decimal places (1599 = 15.99 USD), but some have none (1500 = 1500 JPY) and a few have 3 (12345 = 12.345 KWD)."

Changed12 schema fields changedSep 8, 2026

changedInput schema / properties / fee / description

Previous value: -"The recurring charge for this subscription."New value: +"Recurring charge."

changedInput schema / properties / fee / properties / currencyCode / description

Previous value: -"ISO 4217 currency code (3 letters)."New value: +"ISO 4217 code, three letters."

changedInput schema / properties / fee / properties / value / description

Previous value: -"Amount in the smallest currency unit (e.g. cents for USD)."New value: +"Amount in minor units, e.g. cents."

changedInput schema / properties / name / description

Previous value: -"Display name of the subscription, e.g. 'Netflix' or 'Gym membership'."New value: +"Name, e.g. 'Netflix' or 'Gym membership'."

addedInput schema / properties / name / examples
```
Added value: +[
+  "Netflix"
+]
```

changedInput schema / properties / notes / description

Previous value: -"Free-text notes about the subscription."New value: +"Free-text notes."

addedInput schema / properties / notes / examples

Added value: +[
+  "Family plan, shared with parents"
+]

changedInput schema / properties / remindMe / description

Previous value: -"Whether to send renewal reminders for this subscription"New value: +"Whether to remind the household before each renewal."

addedInput schema / properties / remindMe / examples
```
Added value: +[
+  true
+]
```

changedInput schema / properties / renewalCronExpression / description

Previous value: -"Cron expression describing how often the subscription renews. Must not repeat more frequently than once a day."New value: +"Cron expression for the renewal cadence. No more often than daily."

changedInput schema / properties / status / description

Previous value: -"Lifecycle status of the subscription at creation time."New value: +"Status at creation."

addedInput schema / properties / status / examples
```
Added value: +[
+  "Active"
+]
```

Changed11 schema fields changedJul 14, 2026

addedInput schema / examples

Added value: +[
+  {
+    "fee": {
+      "currencyCode": "USD",
+      "value": 1599
+    },
+    "name": "Netflix",
+    "notes": "Family plan, shared with parents",
+    "remindMe": true,
+    "renewalCronExpression": "0 0 1 * *",
+    "status": "Active"
+  }
+]

addedInput schema / properties / fee / description

Added value: +"The recurring charge for this subscription."

changedInput schema / properties / fee / properties / currencyCode / description

Previous value: -"ISO currency code"New value: +"ISO 4217 currency code (3 letters)."

addedInput schema / properties / fee / properties / currencyCode / examples
```
Added value: +[
+  "USD"
+]
```

changedInput schema / properties / fee / properties / value / description

Previous value: -"Amount in smallest currency unit"New value: +"Amount in the smallest currency unit (e.g. cents for USD)."

addedInput schema / properties / fee / properties / value / examples
```
Added value: +[
+  1599
+]
```

addedInput schema / properties / name / description

Added value: +"Display name of the subscription, e.g. 'Netflix' or 'Gym membership'."

addedInput schema / properties / notes / description

Added value: +"Free-text notes about the subscription."

changedInput schema / properties / renewalCronExpression / description

Previous value: -"Cron expression for renewal"New value: +"Cron expression describing how often the subscription renews. Must not repeat more frequently than once a day."

addedInput schema / properties / renewalCronExpression / examples
```
Added value: +[
+  "0 0 1 * *"
+]
```

addedInput schema / properties / status / description

Added value: +"Lifecycle status of the subscription at creation time."

Changed1 schema field changedJul 3, 2026

addedInput schema / properties / remindMe

Added value: +{
+  "description": "Whether to send renewal reminders for this subscription",
+  "type": "boolean"
+}

First observedJun 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already indicate a non-read-only, non-destructive mutation. The description adds useful domain constraints about recurring vs one-off bills and paymentDate, but it does not disclose broader behavioral effects such as record visibility, duplicate handling, or validation outcomes. No contradiction with annotations.

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?

Three sentences, front-loaded with the core purpose, and every sentence carries distinct information. There is no redundancy or filler.

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?

Given the fully documented 8-parameter schema and the presence of an output schema, the description covers the essential semantics well. The only notable gap is the lack of an explicit when-to-use vs alternatives statement, but the purpose and parameter rules are adequately scoped.

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%, so the baseline is 3. The description largely restates the cron frequency and paymentDate guidance already present in the schema, adding little meaning beyond what the structured property descriptions provide.

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 description clearly names a specific resource ('a bill such as a streaming service or membership') and a verb ('Track'), so an agent understands it creates a subscription-tracking record. It does not explicitly contrast with update_subscription, list_subscriptions, or delete_subscription, leaving sibling differentiation mostly to the tool name.

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 provides concrete usage rules: renewal schedules cannot be more frequent than daily, a bill without a renewal schedule is a one-off, and paymentDate should only be set when money leaves the account on a different day. It does not explicitly say when to prefer a sibling tool, but the parameter-selection guidance is clear and actionable.

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

All haus tools Inspect

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

Need Help?