haus

update_subscription

Update a subscription. Only the fields you send change; for renewalCronExpression, startDate, paymentDate and notes an empty string clears the stored value.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Subscription id from list_subscriptions.
`fee`	No	Recurring charge.
`name`	No	New name.
`notes`	No	Free-text notes. Empty string clears them.
`status`	No	New status.
`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. Empty string clears it.
`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. Empty string clears it.
`renewalCronExpression`	No	Cron expression for the renewal cadence, no more often than daily. Empty string clears it, making the bill a one-off.

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: -[
-  {
-    "id": "0198c1f4b2c07a1b9e4d5f6a7b8c9d0e",
-    "notes": "Paused while travelling",
-    "status": "Paused"
-  }
-]New value: +[
+  {
+    "id": "0198c1f4b2c07a1b9e4d5f6a7b8c9d0e",
+    "notes": "Paused while travelling",
+    "status": "Paused"
+  },
+  {
+    "id": "0198c1f4b2c07a1b9e4d5f6a7b8c9d0e",
+    "paymentDate": "2026-10-03"
+  }
+]

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. Empty string clears it.",
+  "examples": [
+    "2026-10-03"
+  ],
+  "type": "string"
+}

changedInput schema / properties / renewalCronExpression / description

Previous value: -"Cron expression for the renewal cadence, no more often than daily. Empty string clears it."New value: +"Cron expression for the renewal cadence, no more often than daily. Empty string clears it, making the bill a one-off."

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. Empty string clears it.",
+  "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)."

Changed13 schema fields changedSep 8, 2026

changedInput schema / properties / fee / description

Previous value: -"The recurring charge for this subscription. Omit to leave unchanged."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 / id / description

Previous value: -"ID of the subscription to update."New value: +"Subscription id from list_subscriptions."

changedInput schema / properties / name / description

Previous value: -"Display name of the subscription. Omit to leave unchanged."New value: +"New name."

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

changedInput schema / properties / notes / description

Previous value: -"Free-text notes about the subscription. Omit to leave unchanged, or send an empty string to clear the notes."New value: +"Free-text notes. Empty string clears them."

addedInput schema / properties / notes / examples

Added value: +[
+  "Paused while travelling"
+]

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. Omit to leave unchanged, or send an empty string to clear the renewal schedule."New value: +"Cron expression for the renewal cadence, no more often than daily. Empty string clears it."

changedInput schema / properties / status / description

Previous value: -"New lifecycle status for the subscription. Omit to leave unchanged."New value: +"New status."

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

Changed13 schema fields changedJul 14, 2026

addedInput schema / examples

Added value: +[
+  {
+    "id": "0198c1f4b2c07a1b9e4d5f6a7b8c9d0e",
+    "notes": "Paused while travelling",
+    "status": "Paused"
+  }
+]

addedInput schema / properties / fee / description

Added value: +"The recurring charge for this subscription. Omit to leave unchanged."

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 / id / description

Added value: +"ID of the subscription to update."

addedInput schema / properties / id / examples

Added value: +[
+  "0198c1f4b2c07a1b9e4d5f6a7b8c9d0e"
+]

addedInput schema / properties / name / description

Added value: +"Display name of the subscription. Omit to leave unchanged."

addedInput schema / properties / notes / description

Added value: +"Free-text notes about the subscription. Omit to leave unchanged, or send an empty string to clear the notes."

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. Omit to leave unchanged, or send an empty string to clear the renewal schedule."

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

addedInput schema / properties / status / description

Added value: +"New lifecycle status for the subscription. Omit to leave unchanged."

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.7/5.0

Behavior4/5

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

Annotations only say the tool is not read-only and not destructive; the description adds the non-obvious partial-update behavior and the empty-string-clears rule for four fields. It doesn't detail response or error behavior, but the output schema covers the return shape.

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 short sentences, front-loaded with the core operation and then the one non-obvious semantic. No filler or repetition of schema content.

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 9-parameter partial-update tool with full schema coverage and an output schema, the description covers the only behavior an agent might miss (partial updates and clearing). It could mention prerequisites such as the subscription id source, but that is already in the schema's id description.

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 100%, so the baseline is 3. The description earns a 4 by adding the global 'only fields you send change' rule, which the schema's per-field descriptions don't make explicit; the empty-string clearing detail is also called out upfront, even if partly duplicated in property descriptions.

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?

States a specific verb and resource ('Update a subscription') and immediately clarifies that updates are partial. It does not explicitly contrast with create_subscription or delete_subscription, but the verb and resource are unambiguous.

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?

No when-to-use guidance or alternatives are given. The partial-update rule is useful, but the description never says when to choose this over create_subscription or delete_subscription.

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?