Mintline MCP Server

search_receipts

Find receipts by amount range, date range, vendor name, or match status. Quickly locate potential matches for unmatched transactions.

Instructions

Search receipts by amount and date. Search for receipts matching an amount range and/or date range. Useful for finding potential matches for unmatched transactions.

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

Input Schema

Name	Required	Description
`minAmount`	No	Minimum amount
`maxAmount`	No	Maximum amount
`dateFrom`	No	Start date (YYYY-MM-DD)
`dateTo`	No	End date (YYYY-MM-DD)
`search`	No	Search by vendor name
`matchStatus`	No	Filter by match status (default: unmatched)
`limit`	No	Max results (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.9May 6, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It hints at a read-only search (no destructive actions) and notes a default filter status, but lacks details on behavior like pagination or result ordering.

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 concise sentences, front-loaded with purpose and use case, with no redundant or unnecessary information.

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?

The description covers the core functionality and references the key parameters. It could mention result ordering or that the limit parameter controls pagination, but the schema already specifies limit.

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?

All 7 parameters are described in the schema (100% coverage), and the description adds mild context about amount/date ranges and the default unmatched status, but does not add significant new meaning beyond schema.

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?

The description clearly states 'Search receipts by amount and date' and specifies the tool's utility for finding matches for unmatched transactions, distinguishing it from siblings like list_receipts (full list) or get_receipt (single entry).

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?

The description provides a clear use case ('useful for finding potential matches for unmatched transactions') but does not explicitly exclude scenarios or mention alternative tools when other criteria are needed.

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