Skip to main content
Glama
Sign In

Actuary

by pro.actuaryai
OverviewDiscussionsAdmin

Watch a held token

create_mandate

For a token you hold: $0.05 per 7 days over x402 (pay via the REST API or the stdio MCP server). Re-checks a token against the policy about every 30 minutes. Changes (decision, owner, implementation, mint/pause/blacklist, supply) are recorded as events you poll with mandate_events; optionally also POSTed to an https webhook. Every event carries a signed signal: exit, watch or hold. Returns an id and a secret: keep the secret.

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": {
      "token": "<token>"
    },
    "name": "create_mandate"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
policyNoA preset name ("actuary-default-v1", "no-clones-v1") or a policy object. Default: actuary-default-v1. See gate_facts.
exit_onNoWhen the signal says exit: on DENY (default) or on REVIEW too.
webhook_urlNoOptional public https URL. Leave out to poll events instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Substantial disclosure beyond annotations: pricing ($0.05 per 7 days over x402), 30-minute cadence, that changes are persisted as pollable events, that every event carries a signed exit/watch/hold signal, and that an id plus a secret are returned with the secret needing to be kept. It is also consistent with openWorldHint=true (https webhook POSTs) and readOnlyHint=false (it creates a subscription).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded, with the token scope established first and behavior, event flow, and the secret warning in a sensible order. The pricing clause sits early and is somewhat incidental, but nothing is repeated or wasted.

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?

For a stateful, paid, recurring subscription with no output schema, it covers cost, cadence, event delivery, signal semantics, and the returned id/secret. The only gap is lifecycle guidance – nothing says how the mandate is later stopped or inspected, though those live in sibling tools.

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 coverage is 75%, so the schema already documents token, policy, exit_on, and webhook_url. The description adds meaning only for the webhook path ("optionally also POSTed to an https webhook") and indirectly for exit_on via the exit/watch/hold signal vocabulary; policy presets and the review-vs-deny exit choice are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes clear this sets up a recurring re-check of a token against a policy ("Re-checks a token against the policy about every 30 minutes") and mentions the mandate_events sibling for polling. It never says plainly 'create a mandate', so the action verb has to be inferred from the title, but the resource and effect are unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It offers one real routing decision – poll events via mandate_events or supply a webhook – and implies use when you hold a token you want watched. It does not explicitly say when to prefer this over gate, gate_batch, or mandate_status, so the agent must infer the boundary.

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

All Actuary toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources