Capable

Renew subscription

renew_subscription

Destructive

Renew a subscription: advance current_term_started_at and current_term_ends_at forward by one billing cadence (or accept explicit dates), optionally update mrr_cents/seats/plan_name (for renewals with uplift). Writes a subscription_events row of type 'renewed'. Link to the closed-won renewal opportunity_id when available.

When to use: On close-win of a renewal opp. Handles term-date math by cadence.

Example: Renew Acme's Pro Annual subscription for another 12 months at the same MRR.

Input Schema

Name	Required	Description
`id`	Yes	A uuid.
`notes`	No	Free-text note stored on the 'renewed' subscription_events row (e.g. uplift terms); not written to the subscription itself.
`new_seats`	No	Seat count after the renewal — omit to keep the current seats, or pass null to clear them; the 'renewed' event records the resulting seats.
`new_mrr_cents`	No	An integer ≥ 0.
`new_plan_name`	No	Plan name after the renewal (e.g. a tier change); omitted keeps the subscription's current plan_name.
`opportunity_id`	No	A uuid.
`new_current_term_ends_at`	No	Must match /^\d{4}-\d{2}-\d{2}$/.
`new_current_term_started_at`	No	Must match /^\d{4}-\d{2}-\d{2}$/.

Output Schema

Name	Required	Description	Default
`account`	No
`subscription`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 24, 2026

removedInput schema / properties / new_mrr_cents / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  }
-]

addedInput schema / properties / new_mrr_cents / type
```
Added value: +[
+  "number",
+  "string"
+]
```

changedInput schema / properties / new_seats / anyOf

Previous value: -[
-  {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "string"
-      }
-    ],
-    "description": "An integer ≥ 0."
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "An integer ≥ 0.",
+    "type": [
+      "number",
+      "string"
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

Changed1 schema field changedOct 20, 2026
- removedInput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```

Changed5 schema fields changedOct 19, 2026

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / additionalProperties
```
Removed value: -{}
```

changedOutput schema / properties / account / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "current_arr_cents": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "id": {
-        "format": "uuid",
-        "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-        "type": "string"
-      },
-      "lifecycle_stage": {
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      },
-      "renewal_due_at": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "id",
-      "name"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "current_arr_cents": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "id": {
+        "format": "uuid",
+        "type": "string"
+      },
+      "lifecycle_stage": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "renewal_due_at": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "id",
+      "name"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / subscription / additionalProperties
```
Removed value: -{}
```
removedOutput schema / properties / subscription / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```

First observedOct 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare a destructive, non-idempotent write; the description adds genuinely useful side-effect detail — a 'renewed' subscription_events row is written, term math is derived from cadence, and opportunity_id linkage is recorded. The key unstated risk is that repeated invocations advance the term again (idempotentHint=false is never explained), which matters for a renewal tool.

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 mechanic, then a 'When to use' line and a short example — all three sentences earn their place. The example is somewhat redundant with the mechanic sentence but is cheap and concrete.

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 8-param, 1-required mutation with an output schema, the description covers the operation, its side effects, the optional-override paths, and the triggering workflow. Return values need not be explained. Nothing essential for correct invocation is missing beyond the idempotency caveat.

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 baseline is 3, but the description adds real meaning: the cadence-derived dates are the default and explicit new_current_term_* dates are an alternative path, and new_mrr_cents/new_seats/new_plan_name exist specifically for uplift renewals. It doesn't state whether explicit dates must be given as a pair.

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 (renew) and resource (subscription) plus the concrete mechanics: advancing current_term_started_at/current_term_ends_at by one billing cadence, with optional mrr/seats/plan overrides. This clearly distinguishes it from cancel_subscription and the generic update_record siblings.

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?

Explicit trigger given: "When to use: On close-win of a renewal opp," reinforced by a worked example. It does not name an alternative for edge cases (e.g. use update_record for mid-term corrections, or cancel_subscription), so it stops short of full routing guidance.

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

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