Proof Holdings

list_templates

Read-only

List the custom message templates of one sub-account, organized by channel and message type. Templates belong to a sub-account, not to the account: profile_id picks it — omitted, a sub-account key lists its own sub-account and an account-wide key the primary sub-account.

ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT open this tool.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_templates"
  }
}

Input Schema

Name	Required	Description	Default
`profile_id`	No	The sub-account to act on; omitted → your key's sub-account, or the primary sub-account for an account-wide key

Output Schema

Name	Required	Description
`sendable`	No	What a template is sent for. Always sent; absent from an API that predates it.
`profile_id`	No
`custom_templates`	Yes
`available_channels`	Yes
`available_variables`	Yes
`available_message_types`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

changedInput schema / properties / profile_id / description

Previous value: -"The sub-account (project) to act on; omitted → your key's project, or the primary project for an account-wide key"New value: +"The sub-account to act on; omitted → your key's sub-account, or the primary sub-account for an account-wide key"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "available_channels": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "available_message_types": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "available_variables": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "custom_templates": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "body": {
+            "type": "string"
+          },
+          "button_text": {
+            "type": "string"
+          },
+          "button_url_template": {
+            "type": "string"
+          },
+          "channel": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "is_active": {
+            "type": "boolean"
+          },
+          "last_fallback_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "last_fallback_variables": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "message_type": {
+            "type": "string"
+          },
+          "profile_id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "subject": {
+            "type": "string"
+          },
+          "updated_at": {
+            "type": "string"
+          },
+          "version": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          }
+        },
+        "required": [
+          "channel",
+          "message_type",
+          "body"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "profile_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sendable": {
+      "description": "What a template is sent for. Always sent; absent from an API that predates it.",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "channel": {
+            "type": "string"
+          },
+          "message_type": {
+            "type": "string"
+          },
+          "variables": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "channel",
+          "message_type",
+          "variables"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "custom_templates",
+    "available_channels",
+    "available_message_types",
+    "available_variables"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 26, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed2 schema fields changedOct 16, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / profile_id

Added value: +{
+  "description": "The sub-account (project) to act on; omitted → your key's project, or the primary project for an account-wide key",
+  "pattern": "^[0-9a-fA-F]{24}$",
+  "type": "string"
+}

First observedSep 19, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond readOnlyHint=true, the description discloses the return grouping (channel and message type) and, importantly, that the tool is gated behind an authenticated Proof account and that start_login does NOT open it — a non-obvious failure mode worth stating. It does not mention pagination or result limits, so not a 5.

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?

Purpose and scope come first, then the access gate, so the important information is front-loaded. The access paragraph is slightly repetitive ("needs a Proof account" followed by the re-authenticate-and-retry instruction) but every sentence carries actionable content.

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 an output schema present, return shape needn't be described; annotations cover the read-only safety profile; and the single parameter is fully documented. The remaining gap is the absence of guidance about which sibling tool to use for default templates or single-template retrieval.

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 100% and the profile_id description already spells out the omitted-key fallback. The description repeats that same rule ("omitted, a sub-account key lists its own sub-account and an account-wide key the primary sub-account") with only the added framing of templates belonging to a sub-account, not the account — marginal value over the schema, so baseline 3.

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 and resource ("List the custom message templates") plus the scope ("of one sub-account") and the returned organization ("by channel and message type"). The qualifier "custom" implicitly separates it from get_default_templates, but no sibling is named explicitly, so it falls short of a 5.

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 access paragraph tells the agent the precondition for calling (a Proof account, authenticated client), which is real usage guidance. However, it never says when to pick this over get_template, get_default_templates, or preview_template/render_template — the alternative selection is left to inference from the word "custom".

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

All Proof Holdings 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.