OrgLines

Add subscription

add_subscription

Track one of the USER's OWN recurring payments (Netflix, Spotify, gym, hosting, insurance…) and auto-schedule its reminders. This is the user's personal subscription tracking — NOT OrgLines billing. Provide 'title', 'amount', 'period' (weekly/monthly/quarterly/yearly) and 'next_charge_date' (YYYY-MM-DD). Optional: 'currency' (default EUR), 'category' (entertainment/software/fitness/utilities/insurance/hosting/other), 'status' (active/paused/cancelled, default active), 'cancel_url', 'notice_period_days' (German Kündigungsfrist — the cancellation notice window), 'reminder_offset_days' (lead days for the pre-charge reminder, default 3), 'notes'. On create a TZ-003 'charge in N days' reminder is scheduled (server-side — fires with no agent running) plus, when notice_period_days is set, a 'last day to cancel' reminder; both tagged related={type:subscription,id:}. Additive; caller's own record and is written straight away; remove it with the matching delete tool. CONFIRMATION: this tool runs immediately when the caller asks for it — it writes only their own record, and they can undo it from this same surface, so the request is taken as the instruction. You get an ordinary result, not a plan_token. Everything destructive, outbound or financial still proposes and waits.

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": {
      "title": "<title>",
      "amount": "<amount>",
      "period": "<period>",
      "next_charge_date": "<next_charge_date>"
    },
    "name": "add_subscription"
  }
}

Input Schema

Name	Required	Description	Default
`notes`	No
`title`	Yes
`amount`	Yes
`period`	Yes
`status`	No
`category`	No
`currency`	No
`cancel_url`	No
`next_charge_date`	Yes
`notice_period_days`	No
`reminder_offset_days`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false) by disclosing that a server-side TZ-003 reminder fires 'with no agent running', that a second 'last day to cancel' reminder is created when notice_period_days is set, the related={type:subscription,id:<id>} tagging, and that the write is immediate and undoable. The CONFIRMATION block also explains the no-plan_token execution model, which is genuinely useful behavioral context.

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?

Front-loaded with the core purpose, then parameters, then scheduling behavior, then confirmation semantics — a logical order. It is on the long side and repeats the 'own record, written straight away, undoable' idea in both the mid-section and the CONFIRMATION block, which costs some efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter mutation tool with no output schema, the definition covers inputs, defaults, side effects (two reminders, tagging), reversibility, and the confirmation model — an agent has everything needed to call it correctly.

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?

With 0% schema description coverage and 11 parameters, the description carries the full burden and mostly does: it enumerates required fields, formats (YYYY-MM-DD), defaults (EUR currency, active status, 3-day reminder offset), all three enum sets, and explains 'notice_period_days' as the German Kündigungsfrist. Minor gap: the amount field's number-or-string type and cancel_url usage are not explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Track one of the USER's OWN recurring payments... and auto-schedule its reminders') and explicitly excludes the sibling domain ('NOT OrgLines billing'), so an agent can distinguish it from delete/update/get subscription tools without opening a schema.

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?

Gives clear usage context — personal subscriptions such as Netflix, Spotify, gym — and names the cleanup path ('remove it with the matching delete tool'), plus a broad exclusion of destructive/outbound/financial flows. It does not say when to use update_subscription versus re-adding, which keeps it below a 5.

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

All OrgLines 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?