ActionGate

Simulate

simulate

Read-onlyIdempotent

Estimate cost, failure risk, and notable side effects for a proposed action. Paid via x402 or API key credits. Free tier: 20 simulate calls/day per client.

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": {
      "actor": "<actor>",
      "action": "<action>"
    },
    "name": "simulate"
  }
}

Input Schema

Name	Required	Description
`actor`	Yes	Actor metadata for the agent proposing the action.
`action`	Yes	Action payload to evaluate. Additional action-specific fields are accepted as passthrough.
`context`	No	Optional execution context such as chain state, balances, or treasury metadata.
`request_id`	No	Optional caller-supplied request identifier for tracing and receipts.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedMar 27, 2026
- removedInput schema / properties / action / properties / action_type / minLength
```
Removed value: -1
```
- removedInput schema / properties / actor / properties / actor_id / minLength
```
Removed value: -1
```
- changedInput schema / properties / context / additionalProperties
```
Previous value: -{}New value: +true
```
- addedInput schema / properties / context / properties
```
Added value: +{}
```
First observedMar 6, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context about billing and quotas: 'Paid via x402 or API key credits. Free tier: 20 simulate calls/day per client.' This goes beyond the annotations and helps the agent understand cost implications. No contradiction with 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 exceptionally concise: two sentences, zero wasted words. It front-loads the core purpose in the first sentence and adds the critical billing/rate-limit context in the second. Every sentence earns its place.

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 tool with 4 parameters, nested objects, and no output schema, the description is complete enough: it identifies the three output components (cost, failure risk, side effects) and covers key usage context (pricing/free tier). While it doesn't describe return formatting or error cases, the core information needed to invoke and interpret the tool is present.

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 description coverage is 100%, so the input schema fully documents all parameters. The description does not add any additional parameter-level meaning beyond what the schema already provides, meeting the baseline for good schema coverage.

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?

The description clearly states the tool's function: 'Estimate cost, failure risk, and notable side effects for a proposed action.' This specific verb+resource combination distinguishes it from siblings like risk_score, which likely only provides a risk score, and balance/top_up, which deal with funds. The scope is explicit and 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?

The description implies usage for pre-action evaluation ('for a proposed action') and mentions payment/rate limits, but it does not explicitly state when to use this tool versus alternatives like policy_gate or risk_score. No exclusions or alternative tools are named, so guidance is only implied rather than explicit.

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

All ActionGate tools Inspect

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

Need Help?