Skip to main content
Glama

get_invoice_reminder_settings

Read-onlyIdempotent

Read the enabled invoice reminder offsets in days after the due date.

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": "get_invoice_reminder_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the safety profile is covered. The description adds genuine context by disclosing that only enabled offsets are returned and that values are day counts relative to the due date. It does not say anything about ordering or what an empty result means, so it goes modestly beyond the annotations rather than substantially.

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?

A single front-loaded sentence with no filler; the enabling filter and the unit of measurement are both stated up front. Nothing is repeated from the annotations or schema.

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 no-argument read with rich annotations, the description covers what is returned (day offsets measured from the due date, enabled entries only). Without an output schema, a hint about the format (e.g. sorted list of integers) or empty-state behavior would close the remaining gap.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning left to compensate for. The description correctly spends its words on return-value semantics instead of inventing inputs.

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?

Specific verb ('Read') plus a precisely scoped resource ('enabled invoice reminder offsets'), with the unit qualified as 'days after the due date'. It clearly separates itself from non-reminder invoice tools, though it never explicitly contrasts with the sibling reminder-settings readers (appointment, contract, followup).

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

Usage Guidelines3/5

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

The name and resource noun imply the read-reminder-settings context, and the 'enabled' qualifier hints this is the inspection counterpart to the sibling set_invoice_reminder_day. However, no sentence states when to call this versus modifying settings with set_invoice_reminder_day, so usage is only implied.

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