clover-mcp

list_refunds

Read-only

Retrieve refunds within an optional date window (default: today, max 50). Requires PAYMENTS_R permission; does not issue refunds.

Instructions

List refunds within an optional date window (default: today, limit 50).

Clover refunds are separate objects with a positive amount (cents), not negative payments. Card/transaction detail is never included. Requires PAYMENTS_R. This tool does NOT issue refunds.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`date_to`	No
`date_from`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Aug 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare read-only and open-world hints, but the description adds meaningful behavioral context: refunds are separate objects with positive amounts, card/transaction detail is never included, requires PAYMENTS_R, and does not issue refunds. This goes beyond the annotations and sets correct expectations.

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?

Three dense sentences, front-loaded with the primary function. Every sentence earns its place: purpose, domain nuance, permission, and non-action. No unnecessary words.

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 simple list tool with 3 optional params and an output schema, the description covers purpose, defaults, domain specifics, permissions, and exclusions. The output schema handles return-value details, so the description is fully sufficient.

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?

Schema coverage is 0% and there are no per-parameter descriptions, but the description clarifies the 'optional date window (default: today, limit 50)', giving meaning to the date_from/date_to and limit parameters. It does not specify date format, but that is a minor gap for a simple list tool.

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?

Clearly states 'List refunds within an optional date window' with a specific verb and resource. Distinguishes itself from sibling tools by explaining Clover refunds are separate positive-amount objects, not negative payments, and noting card/transaction detail is never included.

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

Usage Guidelines4/5

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

Provides clear context: optional date window, default behavior, and explicitly states 'This tool does NOT issue refunds'—a key exclusion. Also notes the required PAYMENTS_R permission. However, it does not explicitly name alternative tools for related operations (e.g., list_payments), so some guidance is implicit.

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

Deploy Server