Skip to main content
Glama

openentity_mandate_covers

Verify whether a mandate/1 covers a cart/1 (scope, currency, rail, per-purchase and period limits) and whether the purchase needs the owner's approval first. Offline: it does not check the mandate's signature; use openentity_mandate_verify for that.

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": {
      "mandate": "<mandate>",
      "cart": "<cart>"
    },
    "name": "openentity_mandate_covers"
  }
}

Input Schema

NameRequiredDescriptionDefault
cartYes
mandateYes
total_spentNo
period_spentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that the check runs offline and deliberately skips signature verification, which prevents a false sense of cryptographic assurance. However, it says nothing about what the result looks like (boolean vs. detailed reason codes), whether it is read-only, or what happens when limits are exceeded — gaps that matter for a decision tool with zero annotation coverage.

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 the core operation, with the caveat placed after the primary purpose. Every clause carries information; nothing is redundant.

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?

The description explains what is checked but not what is returned, and there is no output schema to fill that gap, so an agent cannot anticipate the response shape for a pass/fail-plus-reason tool. Combined with the undocumented optional parameters, the definition is workable but incomplete for the tool's complexity.

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

Parameters2/5

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

Schema description coverage is 0% and both required parameters are opaque untyped objects, so the description must compensate. It hints at what the mandate contains (scope, currency, rail, limits) and what the cart represents, but the two optional parameters total_spent and period_spent are never mentioned, leaving an agent to guess whether they supply running usage against the period limit.

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?

Names a specific verb (verify) and two specific resources (mandate/1, cart/1), then enumerates exactly which constraints are evaluated: scope, currency, rail, per-purchase and period limits, plus approval requirement. This is clearly separable from sibling openentity_mandate_verify, which the description explicitly names.

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 second sentence gives an explicit when-not condition: signature checks belong to openentity_mandate_verify, not here. That is a genuine routing instruction with a named alternative, though it does not cover other plausible alternatives such as openentity_commerce_check or when this should be run in a purchase flow.

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.