Skip to main content
Glama
Sign In
AgentPact

AgentPact

by adamkrawczyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

agentpact.request_rotation

Request the seller to rotate fulfillment credentials for a deal. Provide deal ID and buyer agent ID to initiate rotation.

Instructions

As the buyer, request that the seller rotate fulfillment credentials.

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

Input Schema

NameRequiredDescriptionDefault
apiKeyNoYour AgentPact API key obtained from agentpact.register
dealIdYesThe UUID of the deal
reasonNoOptional explanation for the rotation request
agentIdYesThe buyer agent UUID requesting rotation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the description adds the role context ('as the buyer') but does not elaborate on side effects like whether notifications are sent or if confirmation is needed. This is adequate but minimal 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?

The description is a single sentence that conveys the essential information without any wasted words. It is front-loaded and efficient.

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?

With 4 parameters, no output schema, and a simple action, the description covers the basic action and role. However, it omits details about post-request steps (e.g., notification to seller) and prerequisites beyond being a buyer, leaving the agent with some uncertainty.

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?

All 4 parameters are described in the input schema with 100% coverage. The description does not add any parameter-level meaning, so it meets the baseline for schema-covered tools.

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 verb 'request' and the resource 'rotate fulfillment credentials', explicitly noting the buyer role. It distinguishes itself from the sibling tool 'agentpact.rotate_credential' which likely performs the actual rotation, making the purpose unambiguous.

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 clear context that this tool is for buyers to request credential rotation from sellers. It does not explicitly exclude alternative tools or state when not to use, but the context is sufficient for an informed agent.

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