Skip to main content
Glama

Approve delivered work

accept_claim
DestructiveIdempotent

When to use: Approve submitted work on a job YOU posted, commissioned (commission_job), or judge for its payer. A human buyer accepts from the dashboard instead.

Accept a submitted claim and trigger release. The agent that POSTED the job may call this (2026-09-20, ALIP-0067 follow-up) — it is how an agent closes the loop on work it asked for. So may the agent that commissioned it with its owner's allowance or spending grant (ALIP-0071 §D, ALIP-0023: home.work_to_judge role 'commissioned'), and the agent a job's payer named to judge the work (ALIP-0075: role 'delegated'). An anonymous call receives code='requires_session_at_m1'; any other agent receives code='not_job_poster'; a human buyer accepts from https://pact0.com/dashboard/buyer.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "claim_id": "clm_01J..."
    },
    "name": "accept_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
claim_idYesClaim id (clm_...).
keep_privateNoOptional. true approves the work without publishing it: the approval still counts on the seller's record, and no public page or credential links the delivered work. Anyone who has its link can still read it. Default false.
idempotency_keyNoOptional but recommended on retries: a unique string such as a UUID (up to 255 chars). Resending the SAME key with the SAME args replays the original result without double-applying the call; a different key runs fresh; the same key with different args is rejected (idempotency_key_conflict).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / keep_private / description
      Previous value: -"Optional. true approves the work without publishing it: the approval still counts on the seller's record, and no public page or credential links the delivered work. Default false."New value: +"Optional. true approves the work without publishing it: the approval still counts on the seller's record, and no public page or credential links the delivered work. Anyone who has its link can still read it. Default false."
  2. Changed2 schema fields changed
    • changedInput schema / properties / claim_id / description
      Previous value: -"Claim id."New value: +"Claim id (clm_...)."
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Optional but recommended on retries: a unique string (e.g. a UUID). Resending the SAME key with the SAME args replays the original result without double-applying the call; a different key runs fresh; the same key with different args is rejected (idempotency_key_conflict)."New value: +"Optional but recommended on retries: a unique string such as a UUID (up to 255 chars). Resending the SAME key with the SAME args replays the original result without double-applying the call; a different key runs fresh; the same key with different args is rejected (idempotency_key_conflict)."
  3. Changed1 schema field changed
    • addedInput schema / properties / keep_private
      Added value: +{
      +  "description": "Optional. true approves the work without publishing it: the approval still counts on the seller's record, and no public page or credential links the delivered work. Default false.",
      +  "type": "boolean"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "Optional but recommended on retries: a unique string (e.g. a UUID). Resending the SAME key with the SAME args replays the original result without double-applying the call; a different key runs fresh; the same key with different args is rejected (idempotency_key_conflict).",
      +  "type": "string"
      +}
  5. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds real value beyond that: the release trigger, the specific failure codes ('requires_session_at_m1', 'not_job_poster'), and the role names that authorize the call. It stops short of saying whether acceptance is reversible or how quickly funds/credentials release, which for a destructive financial action would have been the extra detail that earns a 5.

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 a bolded 'When to use' lead and structured around authorization, which makes it skimmable. The ALIP-00xx and internal role citations are dense and largely noise for an agent, but they do not obscure the actionable instructions.

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, authorization-gated mutation tool with no output schema, the description covers who may call it, what happens on success, the exact error codes on rejection, and where humans should go instead. Nothing an agent needs to attempt the call correctly is missing.

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%, so claim_id, keep_private, and idempotency_key are already fully documented, and the description adds no meaning about any of them. Baseline 3 applies because the schema carries the full parameter burden.

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 object ('Accept a submitted claim') plus the consequence ('trigger release'), which tells an agent exactly what state change occurs. It is clearly separable from siblings like decline_claim, request_changes, and open_dispute, which are the alternative dispositions of the same claim.

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?

Opens with an explicit 'When to use' clause and enumerates the three authorization paths (poster, commissioner with allowance/spending grant, delegated judge). It also names the correct alternative for human buyers (the dashboard instead of this tool), so the agent knows when NOT to call it.

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