Skip to main content
Glama

set_recurring_invoice_renewal

DestructiveIdempotent

Schedule a recurring invoice subscription to end after its current billing period, or let it renew. Confirm the change with the business owner before calling.

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": {
      "id": "<id>",
      "renew": "<renew>"
    },
    "name": "set_recurring_invoice_renewal"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
renewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely new behavior: the change takes effect only at the end of the current billing period rather than immediately, and it requires owner confirmation first. It stops short of saying whether the change can be reversed or what happens to already-issued invoices.

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 sentences, front-loaded with the action and its two outcomes, followed by the prerequisite. Every clause carries information; nothing is redundant.

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

Completeness3/5

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

For a destructive, non-read-only mutation with no output schema and zero schema description coverage, the description covers the key scoping and the confirmation requirement, which is the most important context. It omits reversibility, failure behavior, and disambiguation of the 'renew' boolean values, leaving gaps an agent would want closed.

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 0%, so the description must carry the parameter burden. It implies that 'renew' selects between ending and continuing and that the subscription is identified by 'id', but it never states which boolean value produces which outcome, nor the expected UUID format. Partial compensation only.

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 uses a specific verb and resource ('Schedule a recurring invoice subscription') and states both outcome modes: end after the current billing period, or renew. An agent can tell this is the renewal-state toggle for recurring invoices, distinct from read-only siblings like get_recurring_invoice_history, though it never names an alternative 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?

It gives clear operating context: use this to either stop renewal at period end or keep it renewing, and it adds a concrete precondition ('Confirm the change with the business owner before calling'). What it lacks is any exclusion or named alternative tool for other recurring-invoice operations.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources