Skip to main content
Glama

get_contract_reminder_settings

Read-onlyIdempotent

Read a contract's reminder schedule and number of reminders sent. The next reminder time is in Unix milliseconds when scheduled.

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>"
    },
    "name": "get_contract_reminder_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/closed-world, so the description's added value is in disclosing what comes back (reminder schedule plus count of reminders sent) and the unit of the next reminder time (Unix milliseconds). That unit detail is exactly the kind of thing annotations cannot express. It stops short of saying what happens when no reminder is scheduled.

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 short sentences, front-loaded with the action and resource, then a targeted clarification about time units. No filler and no redundancy with the schema or annotations.

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?

With no output schema, the description carries the return-value burden and does cover the main fields and the Unix-millisecond convention. A simple single-parameter read tool with full read-only annotations does not need much more; only the not-scheduled case is left ambiguous.

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 0% and the single parameter is only typed as a UUID with a pattern, no semantic description. The phrase 'a contract's' implies the id is a contract identifier, which is a small but real addition; it adds no format or lookup guidance beyond that.

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?

States a specific verb and resource: 'Read a contract's reminder schedule and number of reminders sent.' This clearly distinguishes it from the save/update reminder-setting siblings and from the appointment/invoice/followup reminder getters by naming the contract domain. It does not explicitly contrast with those siblings, but the resource is unambiguous.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. The agent must infer from the 'Read' verb and the name alone that this is the retrieval counterpart to save_contract_draft_reminder_settings.

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