Skip to main content
Glama

save_contract_draft_reminder_settings

Idempotent

Set the reminder schedule for a draft contract. Reminders begin after the contract is issued.

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>",
      "enabled": "<enabled>",
      "firstAfterDays": "<firstAfterDays>",
      "repeatDays": "<repeatDays>",
      "maxReminders": "<maxReminders>"
    },
    "name": "save_contract_draft_reminder_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
enabledYes
repeatDaysYes
maxRemindersYes
firstAfterDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already state that this mutates state, is idempotent, and is not destructive. The description adds one useful lifecycle fact: reminders start only after the contract is issued, which frames what firstAfterDays means. It does not say whether the call replaces the existing schedule, what happens when enabled is false, or whether the draft must be in a particular status.

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?

Two short sentences, no padding, and the core purpose comes first. The word count is appropriate for what it covers, even though more detail is needed.

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

Completeness2/5

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

A mutating settings call with five required numeric or boolean parameters, no output schema, and no descriptions in the schema needs a fuller definition. The description leaves the schedule fields' meaning, defaults, bounds behavior, and overwrite semantics unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five required parameters, so the description must carry the meaning, and it does not: enabled, firstAfterDays, repeatDays, and maxReminders are barely mentioned or never mentioned. 'Reminders begin after the contract is issued' hints that firstAfterDays is measured from issuance, which is the only parameter insight given.

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 gives a specific verb and resource: 'Set the reminder schedule for a draft contract.' An agent can distinguish it from the sibling get_contract_reminder_settings by the set-vs-get framing, though that contrast is only implied rather than stated.

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 explicit guidance on when to call this rather than get_contract_reminder_settings or update_contract_draft, and no preconditions (for example, that the contract must still be a draft). The draft/issued wording offers only a faint usage hint.

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