Simpler.Asia

expense_submit

Sends your own draft expense into the approval queue — draft only; an already-submitted or resolved expense refuses CONFLICT, and only the expense's own creator may submit it. Nobody is notified automatically — approvers see it appear in the Team Claims view. NEXT: expense_approve or expense_reject (admin/owner).

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": {
      "id": "<id>"
    },
    "name": "expense_submit"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The expense id (expense_list shows them).
`notes`	No
`status`	No
`vendor`	No
`currency`	No
`ocr_json`	No
`tax_type`	No
`tags_json`	No
`approved_at`	No
`approved_by`	No
`category_id`	No
`receipt_key`	No
`rejected_at`	No
`amount_cents`	No
`expense_date`	No
`submitted_at`	No
`tax_rate_bps`	No
`recurrence_id`	No
`reimbursed_at`	No
`subtotal_cents`	No
`rejection_reason`	No
`tax_amount_cents`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations, the description discloses the conflict behavior on non-draft expenses, the ownership restriction, and the notification behavior ('Nobody is notified automatically — approvers see it appear in the Team Claims view'). These are precisely the operational traits an agent needs before invoking a non-idempotent mutation.

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 compact and front-loaded: the primary action and scope come first, followed by failure conditions and next steps. Every clause carries useful information with no filler.

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?

For a mutation with no output schema and very low schema coverage, the description covers behavior well but leaves the large optional parameter surface unexplained. An agent can understand the operation's business rules, but not whether or how to supply the many optional fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 5%, with 22 parameters and just the required `id` documented in the schema. The description does not explain the meaning or expected use of the other 21 optional fields, nor does it clarify that only `id` is required for submission.

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 states a specific verb and resource: 'Sends your own draft expense into the approval queue.' It immediately scopes the operation to 'draft only' and 'your own,' which distinguishes it from expense_create, expense_update, and the approval siblings.

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

Usage Guidelines5/5

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

It explicitly says when the tool applies ('draft only'), when it will fail ('already-submitted or resolved expense refuses CONFLICT'), who may call it ('only the expense's own creator'), and what comes next ('NEXT: expense_approve or expense_reject'). This gives an agent clear selection and sequencing guidance.

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

All Simpler.Asia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?