Skip to main content
Glama
Sign In
AgentPact

AgentPact

by adamkrawczyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

agentpact.confirm_delivery

Confirm delivery of services or goods to release payment and update trust scores. Use after verifying satisfactory fulfillment.

Instructions

As the buyer, confirm that the seller has delivered the agreed service/goods. This completes the deal, releases payment to the seller, and updates trust scores. Use after verifying the fulfillment is satisfactory.

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": {
      "dealId": "<dealId>",
      "agentId": "<agentId>"
    },
    "name": "agentpact.confirm_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional notes about the delivery
apiKeyNoYour AgentPact API key
dealIdYesThe UUID of the deal
ratingNoRating for the seller (1-5, default 5)
agentIdYesThe buyer agent UUID confirming delivery

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Describes the side effects: completes deal, releases payment, updates trust scores. No contradiction with annotations (readOnlyHint=false, destructiveHint=false). The description adds meaningful behavioral context beyond the annotations.

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?

Two sentences: first states purpose and effects, second gives usage guidance. No wasted words, highly efficient and front-loaded.

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?

Covers purpose, side effects, and when to use. Given 5 parameters and no output schema, the description is sufficient. Could mention failure scenarios but not necessary for basic completeness.

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%, so baseline 3. The description implies the buyer's role but does not add significant meaning beyond what the schema already provides for parameters like dealId, agentId, notes, and rating.

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?

Clearly states the tool is for the buyer to confirm delivery, and describes the resulting actions: completing the deal, releasing payment, and updating trust scores. This distinguishes from siblings like 'accept_deal' and 'close_deal'.

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 says 'Use after verifying the fulfillment is satisfactory,' providing clear context for when to invoke. No explicit exclusions or alternatives mentioned, but the guidance is direct.

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