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.

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

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds valuable behavioral detail beyond those hints: it explicitly states that the tool returns UNKNOWN rather than inferring current offers, and that it depends on observed live-offer facts.

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 sentences with no filler. It front-loads the core action and immediately clarifies the key limitation (UNKNOWN instead of inference), making it easy for an agent to parse quickly.

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

Completeness5/5

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

With 100% schema coverage, output schema present, and annotations covering the safety profile, the description only needs to add intent and behavioral nuance. It does that effectively. Nothing critical is missing for an agent to select and invoke this tool correctly.

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?

All 7 parameters have full descriptions in the schema, so the baseline is 3. The description adds only a coarse grouping ('availability, duration, card, and auto-conversion facts') rather than any new parameter-level meaning, which is acceptable given the high 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 states a specific verb ('Evaluate') and resource ('live US consumer subscription trial offer'), making the tool's purpose immediately clear. It also distinguishes itself from siblings like refund_eligibility and cancellation_penalty by focusing specifically on trial terms.

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 description gives clear context on how to use the tool: supply observed availability, duration, card, and auto-conversion facts. It also warns against expecting inference from static data. However, it does not explicitly name or contrast alternative sibling tools, so it falls short of a 5.

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.