Skip to main content
Glama
jmjeong

Whooing MCP

by jmjeong

whooing_search_entries

Read-only

Search transactions using query, account, amount, and date filters. Find specific entries with keywords or account names.

Instructions

Search transactions with query, account, amount, and date filters. Prefer this for natural-language find/search requests.

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.
Behavior3/5

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

Annotations already provide readOnlyHint=true, indicating a safe read operation. The description adds no contradictory behavior and mentions the search filters, but does not elaborate on pagination, rate limits, or other behavioral specifics. The annotations carry the burden effectively, so a 3 is appropriate.

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 sentences, no wasted words. First sentence covers purpose and key filters; second adds usage guidance. Efficient and front-loaded.

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?

Despite 21 parameters and no output schema, the description is minimal. It does not explain return format, pagination behavior (despite pagination parameters), or default behavior when filters are absent. More detail would be needed for a search tool of this complexity.

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 the baseline is 3. The description does not add meaning beyond listing the filter categories ('query, account, amount, and date'), but the schema already documents each parameter thoroughly.

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 ('Search'), the resource ('transactions'), and the filters ('query, account, amount, and date'). It also differentiates from siblings by recommending it for 'natural-language find/search requests', making its purpose distinct.

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?

Explicitly advises when to use the tool ('Prefer this for natural-language find/search requests'). It does not mention when not to use it or list alternatives, but the guidance is clear and contextually useful.

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