Skip to main content
Glama

openentity_commerce_check

Verify an agent purchase before you accept it (Agent Commerce Check): returns allow, step_up or deny with reasons and an evidence_id kept 400 days. Send the agent's signed HTTP request (method, url, headers; add body or body_b64 when the request was signed over it), the cart/1, the merchant policy, and the mandate (or an OE-Mandate header). Free, no key.

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": {
      "request": "<request>",
      "cart": "<cart>"
    },
    "name": "openentity_commerce_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
cartYescart/1: profile, merchant, agent_did, lines, total, currency, rail, mandate_id
policyNoagent_policy: min_level, require_owner, require_mandate, min_security_band, accept_issuers, min_owner_level; or {merchant: <did>} to use the policy that merchant published
mandateNomandate/1, when not in an OE-Mandate header
requestYes
approvalNo{approval: approval/2.0, verifier_did, request_id}: the owner's approval of this exact cart, after a step_up

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses outcome values, the evidence_id retention period (400 days), and operational prerequisites ('Free, no key'). It does not state whether the call is purely non-mutating, its idempotency, or error behavior, leaving one gap.

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 purpose and return values are front-loaded, and the second sentence packs the required inputs and auth posture into one clause with no filler. Nothing is repeated from the schema verbatim.

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?

With no output schema, the description does explain the return shape in prose (three verdicts plus reasons and evidence_id), which is the key gap-filler. For a 5-parameter, nested-object tool it omits how the approval/2.0 parameter closes a step_up loop, and says nothing about failure or malformed-input handling.

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 already 80%, so the baseline is 3; the description adds real value by stating the mandate may arrive as an OE-Mandate header instead of a parameter, and by conditioning body/body_b64 on how the request was signed. The 'approval' parameter is never mentioned, even though it is tied to the step_up outcome.

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?

States a specific verb and resource ('Verify an agent purchase'), enumerates the decision outcomes (allow, step_up, deny), and names the capability 'Agent Commerce Check'. An agent can tell this is a pre-acceptance purchase authorization check, distinct from generic verification siblings like openentity_verify or openentity_mandate_verify.

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?

'Verify an agent purchase before you accept it' gives a clear trigger point and sequencing. It does not list when-not-to-use or explicitly name an alternative tool, but the precondition is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.