Skip to main content
Glama
jmjeong

Whooing MCP

by jmjeong

whooing_duplicate_candidates

Read-only

Identifies potential duplicate transactions within a date range by grouping entries with matching date, amount, accounts, and item.

Instructions

Find likely duplicate transactions in a date range by grouping same date, amount, accounts, and item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_dateNoStart date (YYYYMMDD). Defaults to 1st of current month.
end_dateNoEnd date (YYYYMMDD). Defaults to today.
section_idNoSection ID. Defaults to WHOOING_SECTION_ID env var.
limitNoMax number of entries to fetch.
account_idsNoReturn entries where either side account ID is in this list.
account_nameNoCase-insensitive account name match, e.g. Game or 네이버페이.
l_account_idNoReturn entries with this left account ID (e.g. expense category).
r_account_idNoReturn entries with this right account ID (e.g. payment account).
min_moneyNoReturn entries with amount greater than or equal to this value.
max_moneyNoReturn entries with amount less than or equal to this value.
item_containsNoCase-insensitive substring match against the item field.
memo_containsNoCase-insensitive substring match against the memo field.
itemNoRaw Whooing item search. Supports exact match, * wildcard, and detail parentheses.
memoNoRaw Whooing memo search. Supports space-separated AND terms and ! exclusions.
queryNoCase-insensitive substring match against item or memo.
keywordsNoAny keyword to match case-insensitively against item or memo.
page_limitNoEntries API page size for paginated search. Defaults to 100.
max_pagesNoMaximum pages to fetch when paginating with the entries max cursor.
max_api_callsNoMaximum Whooing API calls this tool may make. Defaults to 20.
sort_columnNoWhooing entries sort column. Defaults to entry_date.
sort_orderNoWhooing entries sort order. Defaults to desc.
include_memoNoInclude memo in duplicate grouping. Defaults to false.
min_group_sizeNoMinimum matching entries per duplicate group. Defaults to 2.
Behavior3/5

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

Annotations already indicate readOnlyHint=true, so the description correctly aligns with a read operation. However, the description does not disclose additional behavioral traits like potential high API call usage (max_api_calls parameter) or the grouping algorithm's limitations. It adds minimal context beyond the annotation.

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 17-word sentence that is front-loaded with the core purpose. It is efficient but could be slightly more informative without becoming verbose. No unnecessary words.

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 23 parameters, no output schema, and many sibling tools, the description is overly minimal. It does not explain what the output looks like (e.g., groups of entries), how grouping criteria interact, or that it may make multiple API calls. Incomplete for such a complex tool.

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 description coverage is 100%, so all 23 parameters are described in the schema. The tool description mentions grouping by 'date, amount, accounts, and item,' which maps to parameters but does not add new meaning beyond the schema. Baseline of 3 applies.

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 the verb 'Find' and resource 'likely duplicate transactions' with a specific method 'by grouping same date, amount, accounts, and item.' This distinguishes it from sibling tools like whooing_entries (list all) or whooing_search_entries (general search).

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

Usage Guidelines3/5

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

The description implies using it to find duplicates but does not explicitly state when to prefer it over searching manually or using other tools. No exclusions or alternatives are mentioned. Usage context is only implied.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jmjeong/whooing-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server