Skip to main content
Glama

business_expenses

Read-onlyIdempotent

Expense tracker

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": {
      "items": "<items>"
    },
    "name": "business_expenses"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesThe expenses to total. A refund is a negative amount.
mergeCategoriesNotrue treats categories that differ only in case or surrounding spaces as one. Default false (exactly as sent).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / items / items / additionalProperties
      Removed value: -false
    • addedInput schema / properties / items / items / properties / amount / description
      Added value: +"Expense amount as a plain number, for example 42.5."
    • addedInput schema / properties / items / items / properties / category / description
      Added value: +"Expense category, for example Travel."
  2. Changed4 schema fields changed
    • addedInput schema / properties / items / description
      Added value: +"The expenses to total. A refund is a negative amount."
    • addedInput schema / properties / items / items / properties / date
      Added value: +{
      +  "description": "Optional date, YYYY-MM-DD. When any item has one, the response adds byMonth totals.",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}",
      +  "type": "string"
      +}
    • addedInput schema / properties / items / items / properties / description
      Added value: +{
      +  "description": "Optional note; not used in the totals.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / mergeCategories
      Added value: +{
      +  "description": "true treats categories that differ only in case or surrounding spaces as one. Default false (exactly as sent).",
      +  "type": "boolean"
      +}
  3. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds nothing on top: no mention that the operation computes totals, that refunds are negative amounts, or that date presence triggers byMonth output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two words are technically concise but constitute under-specification rather than efficiency. There is no front-loaded statement of the actual operation or output.

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?

This is a calculation tool whose meaningful behavior — summing expenses, treating refunds as negative amounts, adding byMonth totals when dates exist, and case/space-insensitive category merging — is documented only in the schema. For a tool with no output schema, the description should at minimum state that it returns totals.

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% and the nested item fields are documented thoroughly, so the schema carries the parameter burden. The description contributes zero additional meaning about items, amount, category, date, or mergeCategories, so the baseline 3 applies rather than a higher score.

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

Purpose2/5

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

"Expense tracker" restates the tool name rather than stating what the tool does. It never says it totals or summarizes a list of expenses, nor does it distinguish itself from siblings like business_invoice_totals or business_receipt.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent cannot tell from this text whether it should use this tool or business_invoice_totals / business_receipt for a given expense-related request.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources