Privi Agent Survival & Premium

Human approval decision

privi_pro_approval_gate

Read-only

Decide if an action exceeds an explicitly supplied human-approval threshold. PAID ONLY: 5 prepaid credits; production billing required.

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": {
      "amount": "<amount>",
      "threshold": "<threshold>",
      "approved": "<approved>"
    },
    "name": "privi_pro_approval_gate"
  }
}

Input Schema

Name	Required	Description	Default
`amount`	Yes
`approved`	Yes
`threshold`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

B3/5.0

Behavior3/5

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

The annotations already establish that this is a read-only, closed-world operation. The description adds useful paid-operation context with the 5-credit and production-billing note, but it does not clarify whether credits are consumed per call, what the tool returns, or how the `approved` boolean affects behavior.

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 two tight sentences with no wasted wording. The core purpose is front-loaded and the billing constraint follows immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with three undocumented required parameters and no output schema, the description does not explain the return value or the meaning of `approved`. It covers the high-level decision and billing cost but leaves too much of the contract unspecified.

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%, so the description must explain the three required parameters. It echoes the idea of a threshold but does not define `amount` or explain the role of `approved`, leaving key input semantics unclear.

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 states a specific decision verb and resource: deciding whether an action exceeds a human-approval threshold. It is understandable on its own, but it does not distinguish this tool from potential alternatives or clarify how the required `approved` input affects the decision.

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

Usage Guidelines2/5

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

The description gives no explicit guidance about when to use this tool versus alternatives, nor any when-not conditions. The billing note is a prerequisite, not usage guidance.

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

All Privi Agent Survival & Premium 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?