AdvBox

advbox_create_transaction

Cria um lançamento financeiro (receita ou despesa). Obrigatórios: entry_type, amount, date_due, categories_id, debit_account, cost_centers_id e users_id (IDs em advbox_settings).

Bulk support: accepts categories_ids, cost_centers_ids, users_ids, customers_ids, lawsuits_ids for batched execution.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "advbox_create_transaction"
  }
}

Input Schema

Name	Required	Description	Default
`type`	No
`extra`	No
`value`	No
`amount`	No
`date_due`	No
`due_date`	No
`users_id`	No
`users_ids`	No
`entry_type`	No
`description`	No
`lawsuits_id`	No
`customers_id`	No
`date_payment`	No
`lawsuits_ids`	No
`categories_id`	No
`customers_ids`	No
`debit_account`	No
`categories_ids`	No
`cost_centers_id`	No
`cost_centers_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedOct 24, 2026

addedInput schema / properties / amount

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    }
+  ]
+}

addedInput schema / properties / categories_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    }
+  ]
+}

addedInput schema / properties / categories_ids

Added value: +{
+  "items": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      }
+    ]
+  },
+  "type": "array"
+}

addedInput schema / properties / cost_centers_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    }
+  ]
+}

addedInput schema / properties / cost_centers_ids

Added value: +{
+  "items": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      }
+    ]
+  },
+  "type": "array"
+}

addedInput schema / properties / customers_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    }
+  ]
+}

addedInput schema / properties / customers_ids

Added value: +{
+  "items": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      }
+    ]
+  },
+  "type": "array"
+}

addedInput schema / properties / date_due
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / date_payment
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / debit_account

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    }
+  ]
+}

addedInput schema / properties / description
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / entry_type
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / lawsuits_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    }
+  ]
+}

addedInput schema / properties / lawsuits_ids

Added value: +{
+  "items": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      }
+    ]
+  },
+  "type": "array"
+}

addedInput schema / properties / users_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    }
+  ]
+}

addedInput schema / properties / users_ids

Added value: +{
+  "items": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      }
+    ]
+  },
+  "type": "array"
+}

First observedAug 21, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds the prerequisite that related IDs must exist in advbox_settings and that batched execution is possible — useful context — but says nothing about what happens on retry (important given idempotentHint=false) or what the response contains.

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 compact sentences, front-loaded with the purpose, then the required-field checklist, then the bulk note — no filler. The bulk sentence is slightly cryptic about what 'batched execution' changes, but the structure is efficient.

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 20-parameter mutation with no output schema and no annotation detail beyond safety hints, an agent still cannot tell which of the duplicated singular/array parameters to use, which are genuinely required (the schema lists zero), or what a successful call returns. The description covers the most common path but not the full surface.

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 0% across 20 parameters, so the description must carry the load. It meaningfully documents 7 required fields plus 5 bulk array counterparts and the source of IDs (advbox_settings), but leaves aliases and ambiguous pairs unexplained (value vs amount, due_date vs date_due, type, extra, description, date_payment).

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?

States a specific verb and resource: 'Cria um lançamento financeiro (receita ou despesa)', which tells an agent this is a create-transaction tool and even clarifies the two transaction kinds. It does not name a sibling to disambiguate from (e.g. advbox_update_transaction or advbox_create_movement), so it falls short of a 5.

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 usefully enumerates the fields it treats as mandatory and explains that bulk variants exist ('Bulk support: accepts categories_ids...'), which is real usage guidance. However it never states when to use this versus advbox_update_transaction or advbox_create_movement, nor any preconditions beyond where IDs come from.

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

All AdvBox 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.