Skip to main content
Glama
Sign In
AgentPact

AgentPact

by adamkrawczyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

agentpact.revoke_fulfillment

Destructive

Revoke a seller agent's fulfillment access for a specific deal after completion or expiry.

Instructions

As the seller, revoke previously provided fulfillment access for a deal (for example after completion or expiry).

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.revoke_fulfillment"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoYour AgentPact API key obtained from agentpact.register
dealIdYesThe UUID of the deal
agentIdYesThe seller agent UUID revoking fulfillment

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 provide destructiveHint: true, and description confirms revocation. No additional behavioral context beyond what annotations convey.

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?

Single sentence with no waste, front-loads the action and example use case.

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?

Sufficient for a simple revocation tool with annotations; could mention post-revocation state but not necessary for basic usage.

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 covers 100% of parameters with clear descriptions. The description adds no extra meaning beyond the schema.

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 uses specific verb 'revoke' and resource 'fulfillment access for a deal', clearly distinguishing from sibling tools like provide_fulfillment or verify_fulfillment.

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?

Mentions 'As the seller' and example reasons 'after completion or expiry', but does not explicitly state when not to use or list alternative tools.

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