Skip to main content
Glama

Ausgabenlimit · Archiv

archive_business_budget
DestructiveIdempotent

Request retirement of a selected budget frame or role share through its human Owner card. Use update_business_budget to change a cap. Setting a cap to zero blocks positive new spending but does not retire the resource.

Select what retires

Read get_business_budgets for the exact resource. For a whole frame, use its budgetId and revision. For one share, keep the parent budgetId, add its allocationId and use that share’s revision as expectedRevision. The frame revision and numeric work-journal receipt revision cannot replace the share’s revision.

Resolve blockers before preparing

A frame cannot retire with Workspace/ads_* identity, another active overlap, active shares or bound advertising exposure. A share cannot retire with active children. Zero-valued shares/children are still active; retiring a parent never silently retires them. Share retirement leaves the parent cap unchanged.

Preparation retires nothing. Human confirmation irreversibly removes future spending authority, retaining identity, consumption and history without cancelling provider work. Exact replay keeps the original key/revision and returns an old receipt. After uncertainty read get_business_change(proposalId) and the resource; never prepare another request to probe success.

Requires current Owner authority, operator:prepare, accounting:read and operations:read. Role retirement also needs existing work:read/write and Workspace write authority.

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": {
      "budgetId": "<budgetId>",
      "expectedRevision": "<expectedRevision>",
      "requestKey": "<requestKey>"
    },
    "name": "archive_business_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetIdYesExact parent budgetId from this workspace's get_business_budgets. Without allocationId selects an independent General frame; with allocationId selects only that role share. Never a proposal ID.
requestKeyYesRequired caller UUID for this actor/workspace's archive preparation. Reuse the same key with unchanged budgetId and expectedRevision after uncertainty; changed arguments conflict.
allocationIdNoOmit to retire the independent General frame. To retire one role share instead, copy its allocationId together with the same parent budgetId and that allocation's current revision. Active children block retirement.
expectedRevisionYesUnchanged revision from the exact resource read used for this change. Stale revisions require a fresh read and renewed intent; never replace a revision during replay.

Output Schema

NameRequiredDescriptionDefault
reasonNoRejection reason; no requested change was applied.
statusYes
replayedNoOriginal role/archive receipt replay, not proof of current resource or request state. General is not journal-idempotent.
activatesYes
nextActionNo
proposalIdNoExisting stored human-request identity, not a budgetId or allocationId.
presentationNoThe persisted receipt survives an unavailable card. Read the same proposal; never prepare another request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / allocationId
      Added value: +{
      +  "description": "Omit to retire the independent General frame. To retire one role share instead, copy its allocationId together with the same parent budgetId and that allocation's current revision. Active children block retirement.",
      +  "maxLength": 160,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / properties / budgetId / description
      Previous value: -"Exact independent General frame ID from this workspace's get_business_budgets; never a role allocation or request ID."New value: +"Exact parent budgetId from this workspace's get_business_budgets. Without allocationId selects an independent General frame; with allocationId selects only that role share. Never a proposal ID."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructive/idempotent/not-readonly, and the description adds substantial context beyond them: preparation is non-destructive two-phase, human confirmation irreversibly removes future spending authority while retaining identity/consumption/history, and it does not cancel provider work. It also documents replay semantics (same key/revision returns the original receipt) and the explicit prohibition on probing success with a new prepare.

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?

Well front-loaded with a clear verb-first opening sentence and headed sections (select what retires, resolve blockers, preparation semantics). It is dense and somewhat long, with some restatement of the share/child-activeness rule, but nearly every sentence carries decision-relevant information for a destructive two-phase operation.

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

Completeness5/5

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

For a destructive, two-phase, permission-gated tool this covers the missing pieces: required authorities (Owner, operator:prepare, accounting:read, operations:read, plus work:read/write for role retirement), blocker preconditions, confirmation consequences, and recovery after uncertainty. An output schema exists, so return-shape detail is appropriately not repeated.

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 100%, so the baseline is 3; the description adds real value beyond it by explaining that budgetId alone means the General frame while budgetId+allocationId targets a single role share, and that the share's own revision must be used as expectedRevision rather than the frame or work-journal receipt revision. It does not add much about requestKey/format beyond what the schema already says.

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 ('Request retirement of a selected budget frame or role share') and immediately disambiguates from the sibling mutator by naming update_business_budget as the tool for changing a cap. An agent can distinguish retirement from cap-editing without opening either schema.

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?

Explicitly routes the agent: use update_business_budget to change a cap, note that zeroing a cap does not retire, read get_business_budgets for the exact resource, and use get_business_change(proposalId) after uncertainty. It also enumerates when-not conditions via the blocker list (ads_* identity, active overlaps, active shares/children).

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