Skip to main content
Glama
knishioka

freee Accounting MCP Server

by knishioka

freee_get_expense_applications

Retrieve expense applications with filters for status, date, applicant, approver, and amount. Compact mode provides summary statistics for quick overviews.

Instructions

Get list of expense applications (経費精算申請) - Retrieves expense reports with filtering by status, date, applicant, approver, and amount. Supports approval workflow visibility. Use compact mode for summary statistics only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdNoCompany ID (optional, uses FREEE_DEFAULT_COMPANY_ID if not provided)
statusNoFilter by status (draft: 下書き, in_progress: 申請中, approved: 承認済, rejected: 却下, feedback: 差戻し)
startIssueDateNoStart issue date (YYYY-MM-DD)
endIssueDateNoEnd issue date (YYYY-MM-DD)
startTransactionDateNoStart transaction date for line items (YYYY-MM-DD)
endTransactionDateNoEnd transaction date for line items (YYYY-MM-DD)
applicantIdNoApplicant user ID to filter by
approverIdNoApprover user ID to filter by
minAmountNoMinimum total amount filter
maxAmountNoMaximum total amount filter
offsetNoPagination offset
limitNoNumber of results (1-100, default 50)
compactNoWhen true, returns summary statistics only without individual records. Useful for quick overviews.
Behavior3/5

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

No annotations provided, so description must cover behavior. It mentions retrieval and filtering but doesn't explicitly state read-only nature, rate limits, or authentication needs beyond the companyId parameter.

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, front-loaded with key information, no fluff. Every sentence adds value.

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?

13 parameters with no output schema and no annotations. Description covers high-level purpose and filtering but lacks details on pagination, return format, and default behavior.

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 baseline is 3. The description adds the 'compact mode' hint but otherwise repeats schema info.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Get list of expense applications' with specific filtering dimensions. While it doesn't explicitly contrast with the singular 'freee_get_expense_application' sibling, the name implies a list operation.

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 usage for retrieving filtered lists but lacks explicit when-to-use or when-not-to-use guidance. No alternatives or exclusions are mentioned.

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/knishioka/freee-mcp'

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