Skip to main content
Glama

Draft payment-reminder emails

accounting_debtor_reminder
Read-onlyIdempotent

Drafts a polite payment-reminder email (text only — nothing is sent) for each customer with overdue invoices, listing the invoices and amounts. Edit it, then the business sends it — or use accounting_send_invoice_reminder to send GetAccountED's standard branded reminder for one invoice. Read-only. Needs the user's GetAccountED sign-in (they are asked to sign in the first time).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "accounting_debtor_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idNoAccounting practices only: which client's books (an id from accounting_list_my_businesses). Leave out to use the books chosen at sign-in.
customer_nameNoOnly this customer
min_days_overdueNoOnly invoices at least this many days overdue (default 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new context: the output is text only, nothing is sent, a human edits and sends it, and authentication is required on first use. That is exactly the behavioral detail annotations cannot convey.

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?

Three sentences, front-loaded with the core action and the 'nothing is sent' caveat, with no filler. The em-dash parentheticals make it slightly dense, but every clause carries information.

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 a zero-required-parameter drafting tool with no output schema, the description covers what is produced (per-customer email listing invoices and amounts), what is not done (no sending), the follow-up path, and the auth requirement. Nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so all three parameters are already documented in the schema. The description adds only the aggregate notion of 'each customer with overdue invoices' and does not elaborate on business_id, customer_name, or min_days_overdue beyond what the schema states, so the baseline 3 applies.

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 artifact ('Drafts a polite payment-reminder email') plus the scope ('for each customer with overdue invoices, listing the invoices and amounts'). It explicitly distinguishes itself from the sibling accounting_send_invoice_reminder, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Gives the full workflow: draft, edit, then the business sends it — and names the alternative (accounting_send_invoice_reminder) with the condition that selects it (standard branded reminder for one invoice). It also flags the sign-in prerequisite on first use.

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.