Dayze — Life Context

Add Subscription

add_subscription

Add a subscription the user told you about. Records it only: Dayze never signs up with or pays 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": {
      "vendor": "<vendor>",
      "amount": "<amount>",
      "currency": "<currency>",
      "cadence": "<cadence>"
    },
    "name": "add_subscription"
  }
}

Input Schema

Name	Required	Description
`amount`	Yes	Recurring charge per cadence, e.g. 15.99.
`status`	No	The owner's own plan. Dayze never contacts the vendor.
`vendor`	Yes	Vendor name, e.g. Netflix.
`cadence`	Yes	Billing cadence, e.g. monthly.
`currency`	Yes	3-letter code.
`request_id`	No	Client idempotency key (retries return original result).
`idempotency_key`	No	Alias for request_id.
`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.

Changed3 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 / vendor / description
```
Added value: +"Vendor name, e.g. Netflix."
```
AddedNov 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is partly covered; the description still adds real value by clarifying the record-only semantics — no vendor signup, no payment. It also discloses cost and authentication context ('$0.10; API key required'), which the annotations do not.

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 two-sentence core is front-loaded and wastes nothing; the trailing 'Dayze Pro. ($0.10; API key required)' fragment is terse and slightly telegraphic but carries distinct, useful information about tier, cost, and credentials.

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 nine fully documented parameters and an output schema present, the definition only needs to cover behavior the schema cannot — the record-only, no-payment guarantee, which it does clearly. Minor gaps remain on duplicate handling and where the recorded subscription surfaces afterward.

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 every parameter including the status enum and date formats is already documented. The description adds no field-level meaning (e.g., the undecided/keep/cancel distinction) beyond what the schema provides, so it sits at the baseline.

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 ('Add a subscription') and immediately narrows the scope with 'Records it only: Dayze never signs up with or pays the vendor.' It does not name update_subscription as the alternative for modifying an existing entry, so sibling differentiation is left implicit.

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

Usage Guidelines3/5

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

'Add a subscription the user told you about' gives a context for use — new subscriptions the user reports — but there is no exclusion such as 'use update_subscription to change an existing one' and no prerequisite or duplicate-handling guidance beyond the schema's idempotency key.

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.