Dayze — Life Context

Update Subscription

update_subscription

Change a subscription by subscription_id: status on any row, the other fields only on one the user added. Marking cancel is the owner's note to self: Dayze never cancels anything with the vendor. Dayze Pro. ($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": {
      "subscription_id": "<subscription_id>"
    },
    "name": "update_subscription"
  }
}

Input Schema

Name	Required	Description
`amount`	No	Recurring charge per cadence, e.g. 15.99.
`status`	No	The owner's own plan. Dayze never contacts the vendor.
`vendor`	No	Vendor name, e.g. Netflix.
`cadence`	No	Billing cadence, e.g. monthly.
`currency`	No	3-letter code.
`request_id`	No	Client idempotency key (retries return original result).
`idempotency_key`	No	Alias for request_id.
`subscription_id`	Yes	Subscription id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
`last_charge_date`	No	YYYY-MM-DD.
`next_renewal_date`	No	YYYY-MM-DD.

Output Schema

Name	Required	Description
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`message`	No
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`subscription`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 9, 2026
- addedInput schema / properties / amount / description
```
Added value: +"Recurring charge per cadence, e.g. 15.99."
```
- addedInput schema / properties / cadence / description
```
Added value: +"Billing cadence, e.g. monthly."
```
- addedInput schema / properties / subscription_id / description
```
Added value: +"Subscription id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809."
```
- addedInput schema / properties / vendor / description
```
Added value: +"Vendor name, e.g. Netflix."
```
AddedNov 5, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses the cost ($0.10), the auth requirement (API key), and critically that marking cancel never contacts the vendor — clarifying that the mutation is internal bookkeeping, consistent with destructiveHint=false. That is exactly the extra context annotations cannot carry.

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?

The definition is short and front-loads the subscription_id-plus-scope rule, then the cancel semantics, then cost/auth. The cancellation idea is stated twice ('owner's note to self' and 'Dayze never cancels anything with the vendor'), which is mild redundancy but also reinforces a non-obvious point.

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?

With 10 parameters, an output schema, and full schema description coverage, the description covers the things structured fields cannot: the row-level write restriction, what 'cancel' actually means, cost, and auth. Nothing an agent needs in order to call it is missing, though it does not explain idempotency (left entirely to the schema).

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 description coverage is 100%, so the baseline would be 3, but the description adds a per-field permission model the schema does not express — status is writable on any row while the other fields are only writable on user-added subscriptions. It adds no syntax detail for amount or dates, which the schema already covers.

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 gives a specific verb (change) and resource (subscription) keyed on subscription_id, and adds a concrete scope rule: status can be set on any row, the other fields only on rows the user added. That is far beyond a restatement of the title and lets an agent distinguish it from add_subscription. It only stops short of 5 because it never names or contrasts a sibling explicitly.

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?

There is real when-to guidance: use status changes on any subscription, but restrict vendor/cadence/amount/date edits to user-added rows, and treat cancel as an internal note. No explicit alternatives or 'do not use for X' are given, so it falls short of a full 5.

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