freee-chat-mcp-server

create_smart_expense

Register an expense with smart suggestions for account items and tax codes. Automatically categorize based on description and amount.

Instructions

Create expense with smart suggestions for account items and tax codes. Use this for easier expense creation.

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": {
      "company_id": "<company_id>",
      "amount": "<amount>",
      "description": "<description>"
    },
    "name": "create_smart_expense"
  }
}

Input Schema

Name	Required	Description
`amount`	Yes	Expense amount
`company_id`	Yes	Company ID (use suggest_company first if unknown)
`description`	Yes	Expense description
`expense_type`	No	Type of expense for smart categorization. If not provided, will be auto-detected from description.
`transaction_date`	No	Transaction date (YYYY-MM-DD), defaults to today

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 13, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions smart suggestions but does not explain what happens behaviorally (e.g., whether it modifies input, suggests alternatives, or blocks creation). No info on side effects, permissions, or limits.

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?

Two sentences, efficient and front-loaded. Every word earns its place, though a bit more structure could improve clarity.

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 no annotations, no output schema, and 5 parameters (3 required), the description is sparse. It doesn't explain return values, error handling, or the prerequisite of using suggest_company. Incomplete for a create action.

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 minimal parameter meaning beyond the schema (e.g., implies auto-detection of expense_type but this is already in the schema). No extra depth.

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 tool creates expenses with smart suggestions, using a specific verb (create) and resource (expense). It distinguishes itself from the sibling 'create_expense' by highlighting the smart suggestions feature.

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 says 'use this for easier expense creation,' implying a benefit but no explicit guidance on when to use this vs. alternatives like create_expense. No when-not or prerequisites are mentioned.

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

Deploy Server