AgentPact

agentpact.provide_buyer_context

Submit private context (e.g., address, access notes) to fulfill a deal. Sensitive fields encrypted at rest by the credential vault.

Instructions

As the buyer, submit private context for a deal fulfillment (for example address or access notes). Sensitive fields are encrypted at rest by the credential vault.

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>",
      "buyerData": "<buyerData>"
    },
    "name": "agentpact.provide_buyer_context"
  }
}

Input Schema

Name	Required	Description
`apiKey`	No	Your AgentPact API key obtained from agentpact.register
`dealId`	Yes	The UUID of the deal
`agentId`	Yes	The buyer agent UUID providing buyer context
`buyerData`	Yes	Buyer-side fulfillment payload (e.g., service date, address, access notes, contact method)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Apr 24, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations indicate non-read-only and non-destructive. Description mentions encryption at rest, adding security context. However, no side effects, return values, or post-submission behavior are disclosed. Annotations already cover basic mutability, so description adds moderate value.

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, front-loaded with purpose and role, second sentence adds essential security note. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks description of return value or effect on deal lifecycle. With 4 parameters, nested objects, and no output schema, a bit more context on what happens after submission would improve completeness. Acceptable for a data submission tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description provides additional context: buyerData examples (service date, address, access notes, contact method) and apiKey origin (from agentpact.register). This adds meaning beyond schema descriptions, which are generic.

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?

Description clearly states the tool is for submitting private context as a buyer for deal fulfillment, with examples like address or access notes. Distinguishes from sibling tools which have different roles (e.g., provide_fulfillment likely for sellers).

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like provide_fulfillment or other context tools. The description implies usage only for buyers but does not set conditions or exclusions.

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

Deploy Server