Skip to main content
Glama
Sign In
@proof-holdings/mcp-server

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_template

Read-only

Retrieve the message template a sub-account uses for a channel and message type, returning its custom template when set or the default otherwise.

Instructions

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. Set PROOF_API_KEY and restart this server, then call this tool again. start_login does NOT open this tool.

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. Changed3 schema fields changedv1.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • 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 changedv1.7.0
    • 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"
+}
  3. First observedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description stays consistent with that while adding real context: the scope-resolution fallback logic, the fact that the response carries the sub-account in profile_id, and a concrete auth prerequisite (set PROOF_API_KEY, restart the server, and note that start_login does not unlock this tool). The auth/restart caveat is exactly the kind of operational detail annotations cannot express.

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?

The first sentence is front-loaded with the resolution semantics and does the heavy lifting. The second paragraph is operational boilerplate but short and genuinely actionable; nothing is redundant.

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?

An output schema exists so return shape needn't be described, and the description covers resolution behavior and auth prerequisites. It is silent on the no-template / invalid message_type edge case, but that is a minor omission for a three-parameter read tool.

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 profile_id already documents the omitted-value default, so the schema carries the parameter burden. The description adds only modest meaning beyond it — that channel and message_type jointly select the template, and that profile_id also appears in the response to identify the sub-account.

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 ... for a channel and message type') and adds the resolution rule: custom template (scope "project") wins, otherwise the default (scope "default"). That distinguishes it from a plain listing tool, though it never names the close siblings list_templates or get_default_templates explicitly.

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 fallback sentence implies when to use it (you want the effective template actually sent, not the raw catalogue), and the access paragraph tells the agent it needs a Proof account. But there is no explicit 'use X instead when you want Y' routing against get_default_templates, list_templates, or preview_template/render_template.

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

Deploy Server

Other Tools