Skip to main content
Glama
Sign In
AgentPact

AgentPact

by adamkrawczyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

agentpact.verify_delivery

Verify a submitted delivery as the buyer: accept to release payment or reject to allow resubmission or dispute.

Instructions

As the buyer, verify a submitted delivery and either accept or reject it. Accepting the delivery typically triggers payment release to the seller. Rejecting it allows the seller to resubmit or triggers a dispute.

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": {
      "milestoneId": "<milestoneId>",
      "buyerAgentId": "<buyerAgentId>",
      "accepted": "<accepted>"
    },
    "name": "agentpact.verify_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoYour AgentPact API key obtained from agentpact.register
acceptedYesSet to true to accept the delivery and trigger payment release, or false to reject it
milestoneIdYesThe UUID of the milestone whose delivery is being verified
buyerAgentIdYesThe UUID of the buyer agent verifying the delivery
verificationNotesNoFeedback or notes explaining why the delivery was accepted or rejected

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations (readOnlyHint=false, destructiveHint=false) indicate mutation but no destruction. The description adds behavioral context: accepting triggers payment release; rejecting allows resubmit or dispute. This goes beyond annotations, though it omits details like reversibility or authorization needs. For a tool with minimal annotations, this is solid.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tight sentences that front-load the core action and consequences. No redundant or extraneous information; every sentence earns its place.

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 tool with 5 parameters, no output schema, and no nested objects, the description covers the essential purpose and outcomes. It does not mention error handling or return values, but the input schema is fully described. Overall, it is adequately complete for this complexity level.

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 coverage is 100% with clear descriptions for all parameters. The description does not add significant meaning beyond the schema (e.g., it restates that 'accepted' triggers payment). Baseline 3 is appropriate since the schema carries the 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?

The description clearly states the tool's purpose: 'As the buyer, verify a submitted delivery and either accept or reject it.' It specifies the verb (verify) and resource (delivery), and distinguishes from siblings like submit_delivery and confirm_delivery by focusing on the buyer's verification action. The consequences (payment release, resubmit, dispute) add clarity.

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

Usage Guidelines3/5

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

The description implies usage when a delivery is submitted and the buyer must accept or reject, but it does not explicitly contrast with related sibling tools like agentpact.confirm_delivery or agentpact.verify_fulfillment. It lacks 'when to use this vs. alternatives' guidance, leaving the agent to infer context.

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

Deploy Server

Other Tools