Skip to main content
Glama

pact0

by io.github.cloakmaster
OverviewDiscussionsAdmin

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.

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. 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. 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)."
  2. 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"
+}
  3. 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"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructive and idempotent behavior, and the description layers on top: it discloses authorization requirements, the exact error codes for unauthorized callers (requires_session_at_m1, not_job_poster), and the presence of an alternate human path. That is meaningful context beyond what the annotations convey.

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?

The bolded "When to use" is correctly front-loaded and the body is dense but purposeful. Spec citations (ALIP-0067, 2026-09-20, §D, ALIP-0023) are noise that could be trimmed without losing the actionable meaning.

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 destructive, no-output-schema mutation, the description covers eligibility, error outcomes, and the alternate path well. It leaves implicit what "release" produces for the seller (payout timing/format) and the result shape, which an agent closing a work loop might want.

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%, including keep_private semantics and idempotency_key replay rules, so the schema carries the burden. The description adds no additional parameter nuance, which makes the baseline of 3 appropriate.

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?

Starts with a specific verb+resource ("Accept a submitted claim and trigger release") and shares the accept-vs-decline-vs-request_changes decision space with siblings. An agent can tell it apart from decline_claim and request_changes 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 Guidelines5/5

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

Explicitly states WHO may use it (job poster, commissioner with allowance/grant, delegated judge) and names the alternative path for human buyers (the dashboard). The role/eligibility conditions are enumerated rather than implied.

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

All pact0 toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources