Skip to main content
Glama

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.

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": {
      "company_id": "<company_id>",
      "decision_id": "<decision_id>"
    },
    "name": "accept_autopost_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
company_idYes
decision_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / body / anyOf
      Previous 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"
      -  }
      -]New value: +[
      +  {
      +    "description": "Optional ``POST /autopost-decisions/{id}/accept`` body; omit it for other kinds.",
      +    "properties": {
      +      "category_id": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "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"
      +  }
      +]
  2. Changed1 schema field changed
    • 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"
      +  }
      +]
  3. Changed1 schema field changed
    • 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"
      +  }
      +]
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the guardrail override, the 403 refusal for agents, 409/422 failures for closed period, sealed year and unknown account, the held→posted state flip with 409 on repeat, and that accepted_by_kind records the channel as 'mcp'. It omits what a successful response returns and any auth/permission prerequisites beyond the human-vs-agent distinction, so it is strong but not exhaustive.

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 action and effect, then error conditions, then optional body rules — a sensible order with no filler sentences. It is dense to the point of being telegraphic (sentence fragments, heavy backtick markup), which costs a little readability but not a place in the definition.

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?

For a three-parameter mutation with no annotations and no output schema, the definition covers the state machine, refusal modes, and the conditional body payloads an agent would otherwise get wrong. The gap is the return value and any success-shape side effects, which the absent output schema means the description would have had to supply.

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 description coverage is 0% and the nested body properties carry no per-field docs, so the description must compensate — and it does, giving conditional requirements keyed on decision kind: expense:receipt:item: needs employee_id plus category_id, autopost:capitalize: needs fixed_asset_category_id only when the hold has none, and needs_split_source requires reclassify_from_account_code. It leaves company_id, decision_id, useful_life_months and the omitted-body default unexplained, so it is not complete.

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 (accept), a specific resource (a held autopost decision), and the resulting effect (posts the AI's proposal). The parenthetical '(accountant)' and 'held' scope it well enough that an agent can distinguish it from sibling list_autopost_decisions or the generic call_operation 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?

Explicitly frames the use case as one-click acceptance of a held decision and gives the gating condition: a person's accept overrides soft guardrails, an agent's is refused (403) unless the row is agent_acceptable or an expense receipt. It does not name an alternative route (e.g. how to review the held decisions first via list_autopost_decisions, or what to do when refused), so it stops short of a full when-to-use/when-not map.

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