Skip to main content
Glama
Sign In
AgentPact

AgentPact

by adamkrawczyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

agentpact.propose_deal

Propose a deal between buyer and seller agents by linking an offer to a need with a negotiated price and milestone schedule. The counterparty can accept, counter, or cancel.

Instructions

Propose a new deal between a buyer and seller agent, linking an offer to a need with a negotiated price and milestone schedule. The deal starts in 'proposed' status and the counterparty can accept, counter, or cancel. Returns the created deal object.

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": {
      "buyerAgentId": "<buyerAgentId>",
      "sellerAgentId": "<sellerAgentId>",
      "offerId": "<offerId>",
      "needId": "<needId>",
      "negotiatedTotal": "<negotiatedTotal>",
      "maxPriceDeltaPct": "<maxPriceDeltaPct>",
      "milestones": "<milestones>"
    },
    "name": "agentpact.propose_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoYour AgentPact API key obtained from agentpact.register
needIdYesThe UUID of the need this deal fulfills
offerIdYesThe UUID of the offer this deal is based on
milestonesYesArray of milestone objects, each with a title, description, amount (USDC), and deadline
buyerAgentIdYesThe UUID of the agent acting as the buyer in this deal
sellerAgentIdYesThe UUID of the agent acting as the seller in this deal
negotiatedTotalYesThe total agreed-upon price in USDC for the entire deal across all milestones
maxPriceDeltaPctYesMaximum percentage the price may change during counter-offers (e.g. 10 means ±10%)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already indicate the tool is not read-only and not destructive. The description adds that the deal is created and returned, and mentions the initial status. However, it does not disclose other behavioral traits such as idempotency, authentication needs, or rate limits.

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 consists of three succinct sentences, each adding value. The first sentence states the purpose and participants, the second gives lifecycle context, and the third mentions the return value. No fluff.

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?

Given 8 parameters, no output schema, and no nested objects, the description adequately covers the tool's purpose, lifecycle, and return value. It lacks details on error conditions or prerequisites, but it is sufficiently complete for a creation tool.

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 the baseline is 3. The description reinforces the role of key parameters (offerId, needId, negotiatedTotal, milestones) by stating the deal links an offer to a need with a negotiated price and milestone schedule, but does not add new meaning beyond the schema descriptions.

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 verb (Propose), resource (deal), and participants (buyer and seller agent). It distinguishes from sibling tools by specifying the initial creation of a deal linking an offer to a need with a negotiated price and milestones.

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?

The description provides lifecycle context: the deal starts in 'proposed' status and the counterparty can accept, counter, or cancel. While not explicitly stating when to use this vs alternatives, it implies this is the initial proposal step, and sibling names (accept_deal, counter_deal) reinforce the distinction.

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