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

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_platform_summary

Read-only

Retrieve a one-call account snapshot of quota projections, request health, per-channel completion rates, HITL counts, and active API keys to monitor dashboard-level performance.

Instructions

Get a one-call account snapshot: quota with end-of-month projection, request health (pending/completed/expired counts + success rate), per-channel completion rates, HITL counts, and active API key count. The same data the dashboard home renders. The hitl_channels sub-object requires the hitl:read scope.

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
profile_idNoScope the metrics and key counts to one sub-account (24 hex characters); the quota stays account-wide
environmentNoScope request/channel/HITL metrics to test or production data (default: production)

Output Schema

NameRequiredDescriptionDefault
as_ofNoWhen the snapshot was computed (ISO 8601)
quotaNo
next_actionNoMost-pressing account action; null when healthy
top_channelsNo
hitl_channelsNoPresent only with hitl:read scope (JWT always)
request_healthNo
active_api_keysNo
cache_age_secondsNoAlways 0 — computed live
channels_with_zero_completionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / profile_id
      Added value: +{
+  "description": "Scope the metrics and key counts to one sub-account (24 hex characters); the quota stays account-wide",
+  "pattern": "^[0-9a-fA-F]{24}$",
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "active_api_keys": {},
+    "as_of": {
+      "description": "When the snapshot was computed (ISO 8601)"
+    },
+    "cache_age_seconds": {
+      "description": "Always 0 — computed live"
+    },
+    "channels_with_zero_completions": {},
+    "hitl_channels": {
+      "description": "Present only with hitl:read scope (JWT always)"
+    },
+    "next_action": {
+      "description": "Most-pressing account action; null when healthy"
+    },
+    "quota": {},
+    "request_health": {},
+    "top_channels": {}
+  },
+  "type": "object"
+}
  2. First observedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only safety, and the description adds real operational context: a Proof account is required, PROOF_API_KEY must be set with a server restart, and the hitl_channels sub-object needs the hitl:read scope. Not disclosed are rate limits or how partial-scope results degrade.

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?

Front-loaded with the value proposition, then a separated ACCESS block. Slightly redundant phrasing ('Set PROOF_API_KEY and restart this server, then call this tool again') costs a little, but nothing is filler.

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 values needn't be explained, yet the description still summarizes what the snapshot contains. Account prerequisite and scope requirement are both covered; only failure/refresh behavior is left implicit.

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 both parameters are documented in-schema, including the 24-hex pattern, the enum, defaults, and the fact that quota stays account-wide. The description adds no parameter detail beyond the schema; only the hitl:read scope note touches output, not inputs.

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?

States a specific verb and resource ('Get a one-call account snapshot') and then enumerates the exact contents: quota with projection, request health counts, per-channel completion rates, HITL counts, API key count. That enumeration separates it cleanly from siblings like get_usage, get_webhook_stats, and get_current_user.

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 'same data the dashboard home renders' framing plus the access note ('start_login does NOT open this tool') gives clear context on when it applies and steers the agent away from a plausible wrong path. It never names an alternative for narrower questions (e.g. point to get_usage), so it stops short of full when/when-not routing.

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