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

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_request_proofs

Read-only

Retrieve proof tokens for verified assets in a verification request so those assets can be verified offline.

Instructions

Get proof tokens for verified assets in a verification request. Returns proof tokens that can be used for offline verification.

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
idYesVerification request ID

Output Schema

NameRequiredDescriptionDefault
proofsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "proofs": {}
+  },
+  "type": "object"
+}
  2. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a read-only operation. The description adds meaningful behavioral context by explaining that the returned proof tokens can be used for offline verification and by spelling out the account/API-key prerequisite, which is not visible from the annotations.

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 definition is front-loaded with purpose and then access constraints, with no unnecessary wording. Both paragraphs are short and each sentence serves a clear operational purpose.

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, read-only annotation, and fully documented parameter, the description covers the essentials an agent needs. It could still be improved by placing this tool more explicitly relative to proof-token siblings, but the access requirement is a useful addition.

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?

The sole parameter has full schema coverage and is documented as the verification request ID. The description implies the same meaning but adds no syntax, format, or validation details beyond what the schema already provides.

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?

The description uses a specific verb and resource: it gets proof tokens for verified assets within a verification request. That scope clearly distinguishes it from related tools like get_proof_token or validate_proof, though it does not explicitly name those alternatives.

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 prerequisite is clearly stated, including the PROOF_API_KEY requirement and the warning that start_login will not unlock this tool. However, it gives no explicit guidance on when to use this versus sibling tools such as get_proof_status or get_proof_token.

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