mcp-server-smallinvoice

create_reminder

Create a reminder for a contact at a specified date and time, with a title and optional description, and set a recurring interval.

Instructions

Creates new reminder

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": {
      "contact_id": "<contact_id>",
      "date_time": "<date_time>",
      "title": "<title>",
      "interval_value": "<interval_value>",
      "interval_type": "<interval_type>"
    },
    "name": "create_reminder"
  }
}

Input Schema

Name	Required	Description
`contact_id`	Yes	id of a contact
`date_time`	Yes	date and time of event that should be reminded (format: Y-m-d H:i:s)
`title`	Yes	title of reminder
`description`	No	description of reminder
`interval_value`	Yes	value of interval in which reminder will be activated
`interval_type`	Yes	one of: ['hour','day','month']

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already indicate mutation (readOnlyHint=false) and non-destructive nature. The description adds no extra behavioral context, such as side effects, permissions, or open world implications (openWorldHint=true).

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?

The description is a single concise sentence, front-loaded with the core action. It could be expanded slightly for completeness, but remains efficient.

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?

Given the tool has 6 parameters, no output schema, and the description is minimal, key details about reminder behavior, return values, and usage context are missing. The description is insufficient for complete understanding.

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 the description is not required to elaborate on parameters beyond what the schema provides. No additional meaning is added.

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 is clear: 'Creates new reminder' specifies the verb and resource. It distinguishes from siblings by name, but lacks additional context to differentiate from other create tools.

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 guidance on when to use this tool versus alternatives like update_reminder or delete_reminders. No when-not-to-use or context provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server