Skip to main content
Glama
flyingwebie

Moxie CRM MCP Server

by flyingwebie

create_expense

Create an expense record in Moxie with amount, date, description, and optional client/project associations to track costs.

Instructions

Create a new expense record in Moxie

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesExpense date (YYYY-MM-DD format)
amountYesExpense amount
billableNoWhether the expense is billable to client
categoryNoExpense category
clientNameNoClient to associate this expense with
vendorNameNoVendor/merchant name
descriptionYesDescription of the expense
projectNameNoProject to associate this expense with
reimbursableNoWhether the expense is reimbursable
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the action without mentioning permissions, reversibility, side effects, or whether an existing client/project must be associated.

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?

The description is a single sentence that front-loads the action and resource. Zero wasted words, ideal conciseness.

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 9 parameters and no output schema, the one-sentence description is insufficient to understand expected return values or operational details such as whether the expense is draft/final, currency handling, or confirmation 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?

The schema provides 100% description coverage for all 9 parameters, so the description adds no extra meaning beyond the schema. Baseline of 3 applies because the description doesn't need to compensate.

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 uses a specific verb ('Create') and resource ('expense record'), clearly distinguishing it from sibling tools like create_invoice or create_client. It unambiguously states the tool's purpose.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool vs alternatives, nor any exclusions or prerequisites. The description only states what it does, not the context in which it should be chosen.

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/flyingwebie/withmoxie-mcp-server'

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