Skip to main content
Glama
Sign In

Proof Holdings

by holdings.proof
OverviewDiscussionsAdmin

get_template

Read-only

Get the template a sub-account sends for a channel and message type: its custom template if set (scope "project"), otherwise the default (scope "default"). The response names the sub-account in profile_id.

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

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": {
      "channel": "<channel>",
      "message_type": "<message_type>"
    },
    "name": "get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYesMessage channel
profile_idNoThe sub-account to act on; omitted → your key's sub-account, or the primary sub-account for an account-wide key
message_typeYesMessage type (e.g. verification_request, login_request)

Output Schema

NameRequiredDescriptionDefault
scopeNo`project` — the sub-account's own template; `default` — the platform default it falls back to.
templateNoMessage template
is_customNo
profile_idNoThe sub-account resolved for this request; null for an account with no sub-account yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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": {
+    "is_custom": {},
+    "profile_id": {
+      "description": "The sub-account resolved for this request; null for an account with no sub-account yet."
+    },
+    "scope": {
+      "description": "`project` — the sub-account's own template; `default` — the platform default it falls back to."
+    },
+    "template": {
+      "description": "Message template"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  3. Changed1 schema field changed
    • 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"
+}
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Placeholder

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?

Two short blocks, with the resolution rule front-loaded in the first sentence and access requirements isolated in the second. Every sentence carries information; there is no filler or repetition of the tool name.

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?

Because an output schema exists, the description need not enumerate return fields, and it still surfaces the one return detail an agent may need (profile_id names the sub-account). Combined with the auth note and fallback rule, an agent has what it needs to invoke correctly; only explicit routing against list_templates/get_default_templates 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 all three parameters are already documented in structured fields, establishing a baseline of 3. The description adds the scope-resolution behavior behind channel/message_type and notes that profile_id is echoed in the response, which is modest added meaning rather than new syntax or format detail.

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 (get the template) and immediately defines the resolution rule: the sub-account's custom template when scope is "project", otherwise the default with scope "default". That fallback semantics distinguishes it from the more generic get_default_templates and list_templates siblings, though it never names them explicitly.

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?

Provides a clear usage precondition (needs a Proof account, authenticate this client first) and an explicit negative (

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

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