Decide Policy Notaries

Check trial terms

trial_terms

Read-onlyIdempotent

Evaluate a live US consumer subscription trial offer. Supply observed availability, duration, card, and auto-conversion facts; the tool returns UNKNOWN instead of inferring current offers from static data.

Input Schema

TableJSON Schema

Name	Required	Description
`plan`	Yes	Plan type. Currently only 'individual' plans are supported.
`region`	Yes	Region code. Currently only 'US' is supported.
`vendor`	Yes	Vendor identifier (lowercase, underscore-separated).
`offer_confirmed`	No	For account- or promotion-specific trials, whether a live offer has been confirmed for this account.
`observed_trial_days`	No	Trial duration shown by the confirmed live offer. Required when offer_confirmed is true for a variable offer.
`observed_auto_converts`	No	Whether the confirmed live offer converts to a paid subscription after the trial.
`observed_card_required`	No	Whether the confirmed live offer requires a payment card.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes
`vendor`	No
`message`	Yes
`verdict`	Yes
`trial_days`	No
`source_hash`	No
`evaluated_at`	No
`auto_converts`	No
`card_required`	No
`rules_version`	No
`policy_version`	No
`automation_safe`	No
`policy_evidence`	No
`rulebook_result`	No
`trial_available`	No
`required_context`	No
`policy_source_url`	No
`policy_last_checked`	No
`policy_source_notes`	No
`policy_last_verified_utc`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026
- changedOutput schema / properties / policy_last_verified_utc / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed2 schema fields changedSep 6, 2026

addedOutput schema / properties / automation_safe
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / policy_evidence

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "checked_at": {
+      "type": "string"
+    },
+    "current": {
+      "type": "boolean"
+    },
+    "evaluated_at": {
+      "type": "string"
+    },
+    "policy": {
+      "enum": [
+        "refund",
+        "cancel",
+        "return",
+        "trial"
+      ],
+      "type": "string"
+    },
+    "policy_version": {
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "schema_version": {
+      "enum": [
+        "policy_evidence_v1"
+      ],
+      "type": "string"
+    },
+    "snapshot_generated_at": {
+      "type": "string"
+    },
+    "snapshot_hash": {
+      "type": "string"
+    },
+    "source_hash": {
+      "type": "string"
+    },
+    "source_url": {
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "current",
+        "expired",
+        "unavailable",
+        "review_required"
+      ],
+      "type": "string"
+    },
+    "valid_until": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "vendor": {
+      "type": "string"
+    },
+    "verified_at": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "schema_version",
+    "policy",
+    "vendor",
+    "status",
+    "reason",
+    "current",
+    "evaluated_at"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedJul 16, 2026

addedInput schema / properties / observed_auto_converts

Added value: +{
+  "description": "Whether the confirmed live offer converts to a paid subscription after the trial.",
+  "type": "boolean"
+}

addedInput schema / properties / observed_card_required

Added value: +{
+  "description": "Whether the confirmed live offer requires a payment card.",
+  "type": "boolean"
+}

First observedJul 16, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and closed-world scope, so the description does not need to restate them. It adds a genuinely non-obvious behavioral trait: the tool returns UNKNOWN rather than inferring current offers from static data, which tells the agent not to expect a best-guess fallback.

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 with no filler: the first establishes purpose and scope, the second establishes the input contract and the UNKNOWN behavior. Purpose is front-loaded ahead of the secondary detail.

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 seven parameters, full schema coverage, an output schema, and rich annotations, the description only needs to carry purpose and the distinctive UNKNOWN fallback behavior, which it does. It could note the account- or promotion-specific nature of certain trials more explicitly, but nothing critical to calling it correctly is missing.

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 enum constraints, required fields, and per-parameter meanings are fully documented in the schema. The description restates the observed fact categories (availability, duration, card, auto-conversion) but adds no format or dependency detail beyond that, which fits the baseline 3 when the schema does the work.

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?

States a specific verb (evaluate) and resource (live US consumer subscription trial offer), which cleanly separates it from cancellation_penalty, refund_eligibility, and return_eligibility. It also signals an input requirement (observed facts). It stops short of naming how it differs from those siblings directly, but the resource scope is 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 when to use it (you must have observed availability, duration, card, and auto-conversion facts) and the condition where the tool is appropriate versus guessing from static data. However, it never explicitly routes the agent to or away from the sibling tools, so usage is only implicitly framed.

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

All Decide Policy Notaries 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.