Mintline MCP Server

confirm_matches

Confirm multiple proposed matches at once for a statement. Batch-confirm match candidate IDs to link receipts with transactions.

Instructions

Confirm multiple matches. Confirm multiple proposed matches at once. Useful for batch-confirming all proposed matches for a statement.

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": {
      "ids": "<ids>"
    },
    "name": "confirm_matches"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	Array of match candidate IDs to confirm

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.9May 6, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It describes a write operation (confirm) but doesn't disclose side effects like irreversibility, changes to statement status, or permission requirements. Adequate but not thorough.

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?

Three sentences with no redundancy. Could be slightly more structured but is efficient and front-loaded with the core purpose.

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

Completeness3/5

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

Given simple tool with one parameter and no output schema, description covers basic functionality. However, lacks information on what happens after confirmation (e.g., effects on matches, user feedback) which a complete description would include.

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% and parameter 'ids' is described well in schema. Description doesn't add much beyond schema, but baseline 3 is appropriate since schema already provides sufficient semantics.

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?

Description uses specific verb 'confirm' and resource 'matches', and explicitly states 'multiple' to distinguish from sibling 'confirm_match'. It also mentions batch use case for a statement, providing clear scope.

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?

States it's 'useful for batch-confirming all proposed matches for a statement', implying when to use it over single confirm. Lacks explicit when-not-to-use or alternatives, but context is clear enough.

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