Skip to main content
Glama

set_invoice_reminder_day

DestructiveIdempotent

Enable or disable automatic overdue invoice emails for one supported offset in days after the due date. This changes the schedule for the entire approved business.

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": {
      "day": "<day>",
      "enabled": "<enabled>"
    },
    "name": "set_invoice_reminder_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYes
enabledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnly=false and idempotent=true, so the safety profile is covered. The description earns credit for adding the blast radius — the change applies to the whole approved business — which is the key side effect an agent needs before mutating global settings. It does not say whether disabling cancels already-scheduled emails.

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 tight sentences with the action front-loaded and the scope caveat second. No filler wording anywhere.

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?

For a two-parameter setter with annotations and no output schema, this covers what changes and at what scope. Missing only the permission requirement and the effect on pending reminder emails, both relevant given the destructive hint.

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 0%, so the description must carry the param meaning, and it does explain that "day" is an offset in days after the due date, which the bare enum [3,7,14] does not convey. "Enable or disable" maps to the boolean, though the specific allowed offsets are left entirely to the schema.

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?

"Enable or disable automatic overdue invoice emails for one supported offset in days after the due date" names a specific verb pair and resource, and the scope line ("entire approved business") separates it from the read-side sibling get_invoice_reminder_settings. It stops short of naming an alternative explicitly, so a 4 rather than a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of pairing with get_invoice_reminder_settings to read the current schedule before changing it. The only constraint offered is "one supported offset," which is a limitation, not usage guidance.

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