Zeno

accept_autopost_decision

One-click accept of a held decision (accountant) — posts the AI's proposal.

A person's accept overrides the soft guardrails. An agent's is refused (403) unless the row is agent_acceptable or an expense receipt. Closed period, sealed year, unknown account: 409/422. The row flips held → posted (again: 409); accepted_by_kind records the channel (mcp over MCP).

Optional body: expense:receipt:item: needs employee_id + category_id; autopost:capitalize: needs fixed_asset_category_id when the hold has none, and needs_split_source a reclassify_from_account_code.

Input Schema

Name	Required	Description	Default
`body`	No
`company_id`	Yes
`decision_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

changedInput schema / properties / body / anyOf

Previous value: -[
-  {
-    "description": "Optional ``POST /autopost-decisions/{id}/accept`` body.\n\nTwo paths read it. The ``expense:receipt:item:`` claim path needs an employee\nand a category (both NOT NULL on the claim plane). The ``autopost:capitalize:``\npath needs a ``fixed_asset_category_id`` when the hold could not resolve one —\na missing category is a 422, never a guess, because the wrong category posts\nthe cost to the wrong balance-sheet account and depreciates it into the wrong\nexpense. The capitalize path may need a third fact:\n``reclassify_from_account_code`` when the hold is a mixed-invoice split whose\nsource line did not resolve (``needs_split_source``) — again a 422 without it,\nnever a guess. Omit the body entirely for every other decision kind (backward\ncompatible).",
-    "properties": {
-      "category_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "confirm_not_card_statement": {
-        "default": false,
-        "type": "boolean"
-      },
-      "employee_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "fixed_asset_category_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "reclassify_from_account_code": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "separate_document": {
-        "default": false,
-        "type": "boolean"
-      },
-      "useful_life_months": {
-        "anyOf": [
-          {
-            "minimum": 1,
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Optional ``POST /autopost-decisions/{id}/accept`` body; omit it for other kinds.",
+    "properties": {
+      "category_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "confirm_not_card_statement": {
+        "default": false,
+        "type": "boolean"
+      },
+      "employee_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "fixed_asset_category_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "reclassify_from_account_code": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "separate_document": {
+        "default": false,
+        "type": "boolean"
+      },
+      "useful_life_months": {
+        "anyOf": [
+          {
+            "minimum": 1,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed1 schema field changedOct 13, 2026

changedInput schema / properties / body / anyOf

Previous value: -[
-  {
-    "description": "Optional ``POST /autopost-decisions/{id}/accept`` body.\n\nTwo paths read it. The ``expense:receipt:item:`` claim path needs an employee\nand a category (both NOT NULL on the claim plane). The ``autopost:capitalize:``\npath needs a ``fixed_asset_category_id`` when the hold could not resolve one —\na missing category is a 422, never a guess, because the wrong category posts\nthe cost to the wrong balance-sheet account and depreciates it into the wrong\nexpense. The capitalize path may need a third fact:\n``reclassify_from_account_code`` when the hold is a mixed-invoice split whose\nsource line did not resolve (``needs_split_source``) — again a 422 without it,\nnever a guess. Omit the body entirely for every other decision kind (backward\ncompatible).",
-    "properties": {
-      "category_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "confirm_not_card_statement": {
-        "default": false,
-        "type": "boolean"
-      },
-      "employee_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "fixed_asset_category_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "reclassify_from_account_code": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "useful_life_months": {
-        "anyOf": [
-          {
-            "minimum": 1,
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Optional ``POST /autopost-decisions/{id}/accept`` body.\n\nTwo paths read it. The ``expense:receipt:item:`` claim path needs an employee\nand a category (both NOT NULL on the claim plane). The ``autopost:capitalize:``\npath needs a ``fixed_asset_category_id`` when the hold could not resolve one —\na missing category is a 422, never a guess, because the wrong category posts\nthe cost to the wrong balance-sheet account and depreciates it into the wrong\nexpense. The capitalize path may need a third fact:\n``reclassify_from_account_code`` when the hold is a mixed-invoice split whose\nsource line did not resolve (``needs_split_source``) — again a 422 without it,\nnever a guess. Omit the body entirely for every other decision kind (backward\ncompatible).",
+    "properties": {
+      "category_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "confirm_not_card_statement": {
+        "default": false,
+        "type": "boolean"
+      },
+      "employee_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "fixed_asset_category_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "reclassify_from_account_code": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "separate_document": {
+        "default": false,
+        "type": "boolean"
+      },
+      "useful_life_months": {
+        "anyOf": [
+          {
+            "minimum": 1,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 11, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With zero annotations the description carries the full burden and does so richly: the held → posted state flip, 409 on repeat accept, 409/422 for closed period, sealed year and unknown account, the 403 authorization split between human and agent, and the accepted_by_kind audit field (mcp over MCP). Nothing about safety or side effects is left to guess.

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?

Front-loaded with the core action, then error codes, then body variants — a sensible order where every sentence carries information. RST-style double-backtick markup and telegraphic fragments ('and ``needs_split_source`` a ``reclassify_from_account_code``') make it denser to parse than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A conditional-body mutation tool with no annotations and no output schema, and the description covers the correctness-critical pieces: authorization, failure modes, state transition and per-kind body requirements. What it omits is the success response shape and the meaning of the remaining body flags, which an agent would have to infer.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it does for the hardest part: body requirements are spelled out per hold kind — expense:receipt:item: needs employee_id + category_id, autopost:capitalize: needs fixed_asset_category_id when absent and needs_split_source needs reclassify_from_account_code. It leaves separate_document, useful_life_months and confirm_not_card_statement undocumented, so the conditional `body` object is only partially covered.

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?

States a specific verb and resource ('accept of a held decision') plus the concrete effect — 'posts the AI's proposal' — so an agent knows exactly what changes. The 'held' qualifier and the sibling list_autopost_decisions make the boundary obvious without opening a schema.

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

Usage Guidelines4/5

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

Gives strong when-it-works / when-it-fails guidance: a person's accept overrides guardrails, an agent's is refused (403) unless the row is agent_acceptable or an expense receipt. It does not name an alternative tool to use when the row is not agent-acceptable, so the fallback path is left implicit.

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

All Zeno 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?