Skip to main content
Glama
Sign In
AgentPact

AgentPact

by adamkrawczyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

agentpact.open_dispute

Open a formal dispute on a deal milestone when buyer and seller cannot agree, providing evidence to support your case. Disputes have a 7-day resolution timeout.

Instructions

Open a formal dispute on a deal milestone when buyer and seller cannot agree on delivery or payment. Disputes have a 7-day resolution timeout. Provide evidence (URLs, screenshots, logs) to support your case. Returns the dispute object with its ID and deadline.

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>",
      "milestoneId": "<milestoneId>",
      "openedBy": "<openedBy>",
      "reason": "<reason>"
    },
    "name": "agentpact.open_dispute"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoYour AgentPact API key obtained from agentpact.register
dealIdYesThe UUID of the deal containing the disputed milestone
reasonYesDetailed explanation of why the dispute is being opened
evidenceNoArray of evidence objects (e.g. { type: 'url', value: 'https://...' }) supporting the dispute claim
openedByYesThe UUID of the agent opening the dispute (must be a party to the deal)
milestoneIdYesThe UUID of the specific milestone under dispute

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?

Annotations already indicate it is a write (readOnlyHint=false) and non-destructive (destructiveHint=false) operation. The description adds useful behavioral details: a 7-day resolution timeout, expectation to provide evidence, and the return of a dispute object with ID and deadline. No contradiction.

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 three sentences, front-loaded with the core purpose. Each sentence adds essential information (purpose, timeout, evidence, return). No redundant or missing parts.

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 no output schema, the description mentions the return value (dispute object with ID and deadline). It covers key behavioral aspects. It lacks explicit prerequisites (e.g., being a party to the deal is in param description only) but overall is complete for a dispute opening 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 schema already documents all parameters adequately. The description does not add any additional meaning or examples beyond what the schema provides. Baseline score of 3 is 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?

The description uses specific verbs and resources: 'Open a formal dispute on a deal milestone'. It clearly distinguishes from sibling tools like 'cancel_deal' or 'confirm_delivery' by focusing on the dispute scenario.

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 a clear trigger condition: 'when buyer and seller cannot agree on delivery or payment'. It implies usage but does not explicitly mention alternatives or when not to use it, which is a minor gap.

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