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

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

export_authorizations

Read-only

Export authorization records as CSV or JSON with date range and status filters to support audits and reporting.

Instructions

Export authorizations as CSV or JSON. Supports date range and status filtering. Maximum 10,000 records.

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
toNoEnd date filter (ISO 8601)
fromNoStart date filter (ISO 8601)
formatNoExport format (default: json)
statusNoFilter by status

Output Schema

NameRequiredDescriptionDefault
dataNo
totalNo

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": {
+    "data": {},
+    "total": {}
+  },
+  "type": "object"
+}
  2. First observedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, and the description adds important operational details beyond that: a Proof account is required, PROOF_API_KEY must be set with a server restart, start_login is insufficient, and exports are capped at 10,000 records. It does not describe truncation behavior when the cap is reached, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core export capability, followed by a compact access note. Every sentence adds actionable information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an export tool with an output schema and fully documented parameters, the description covers capability, filters, formats, record limit, and authentication prerequisites. Nothing essential for correct invocation 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%, including enum values for format and status, so the schema already carries parameter meaning. The description reinforces date range and status filtering but adds no syntax or format details beyond what the schema provides.

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?

The description states a specific verb and resource — export authorizations — plus supported formats and filtering scope. It clearly distinguishes exporting from sibling listing tools like list_authorizations.

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?

It gives clear usage context: export as CSV or JSON with optional date-range and status filters, capped at 10,000 records. It does not explicitly name alternatives or when not to use this tool, but the export framing is sufficiently clear.

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