Skip to main content
Glama
ProofStreamai

ProofStream MCP Server

Official

proofstream_check_status

Check the status of a verification request by case ID to see if it is pending, confirmed, scheduled, in progress, completed, or cancelled.

Instructions

Check the status of a ProofStream verification request by case ID.

Status values:

  • pending_review: Request received, awaiting ProofStream acceptance

  • confirmed: Accepted, payment captured, verification scheduled

  • scheduled: Verification date/time confirmed

  • in_progress: Verifier on-site, livestream active (if requested)

  • completed: Verification done, report delivered to email

  • cancelled: Request declined (no charge)

When status is "completed", the full evidence report and invoice have been emailed to the address provided at submission.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
case_idYesCase ID returned from proofstream_submit_request (e.g., PS-ABC123)

Implementation Reference

  • The checkStatus async function that executes the proofstream_check_status tool logic. It takes a case_id, calls the ProofStream API endpoint /api/cases/{caseId}/status, and returns structured status information including case_id, status, status_label, service, submitted_at, and a human-readable message via getStatusMessage().
    async function checkStatus(args: Record<string, unknown>): Promise<string> {
      const caseId = String(args.case_id).toUpperCase();
      const res = await fetch(`${PROOFSTREAM_API}/api/cases/${caseId}/status`);
      
      if (!res.ok) {
        return JSON.stringify({ error: `Case ${caseId} not found`, status: res.status });
      }
    
      const data = await res.json() as Record<string, unknown>;
      return JSON.stringify({
        case_id: data.case_id,
        status: data.status,
        status_label: data.status_label,
        service: data.service,
        submitted_at: data.submitted_at,
        message: getStatusMessage(String(data.status)),
      });
    }
  • Input schema for proofstream_check_status: requires a string 'case_id' (e.g., PS-ABC123) as the only input parameter.
    inputSchema: {
      type: 'object',
      required: ['case_id'],
      properties: {
        case_id: { type: 'string', description: 'Case ID returned from proofstream_submit_request (e.g., PS-ABC123)' }
      }
    }
  • src/index.ts:101-128 (registration)
    Tool definition registration in the TOOLS array with name 'proofstream_check_status', description of status values, and inputSchema.
      {
        name: 'proofstream_check_status',
        description: `Check the status of a ProofStream verification request by case ID.
    
    Status values:
    - pending_review: Request received, awaiting ProofStream acceptance
    - confirmed: Accepted, payment captured, verification scheduled
    - scheduled: Verification date/time confirmed
    - in_progress: Verifier on-site, livestream active (if requested)
    - completed: Verification done, report delivered to email
    - cancelled: Request declined (no charge)
    
    When status is "completed", the full evidence report and invoice have been
    emailed to the address provided at submission.`,
        inputSchema: {
          type: 'object',
          required: ['case_id'],
          properties: {
            case_id: { type: 'string', description: 'Case ID returned from proofstream_submit_request (e.g., PS-ABC123)' }
          }
        }
      },
      {
        name: 'proofstream_get_pricing',
        description: 'Get current ProofStream pricing and service details without making a request.',
        inputSchema: { type: 'object', properties: {} }
      }
    ];
  • src/index.ts:253-261 (registration)
    The CallToolRequestSchema switch-case that routes the 'proofstream_check_status' tool name to the checkStatus handler function.
      case 'proofstream_check_status':
        result = await checkStatus(toolArgs);
        break;
      case 'proofstream_get_pricing':
        result = getPricing();
        break;
      default:
        throw new Error(`Unknown tool: ${name}`);
    }
  • Helper function getStatusMessage() that maps status strings (pending_review, confirmed, scheduled, in_progress, completed, cancelled, etc.) to human-readable messages used by checkStatus.
    function getStatusMessage(status: string): string {
      const messages: Record<string, string> = {
        pending_review: 'Your request is under review. ProofStream will respond within a few hours.',
        new: 'Request received and queued for review.',
        reviewing: 'ProofStream is reviewing your request and may reach out with questions.',
        quoted: 'A quote has been sent to your email for review.',
        confirmed: 'Verification accepted and payment captured. Scheduling underway.',
        scheduled: 'Verification date confirmed. Verifier will arrive as scheduled.',
        in_progress: 'Verification is underway. If you requested livestream, check your email for watch credentials.',
        completed: 'Verification complete. Your report and invoice have been emailed to you.',
        cancelled: 'Request was not accepted. No charge was made.',
      };
      return messages[status] || 'Unknown status';
    }
Behavior5/5

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

With no annotations provided, the description fully bears the burden of behavioral disclosure. It lists all possible status values and their meanings, including what happens when completed (report and invoice emailed), providing comprehensive behavioral transparency.

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 concise and well-structured, with a clear opening sentence followed by bullet points for statuses. Every sentence is informative with no redundancy.

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?

The description is complete for a status-checking tool: it explains the input, the status values, and the outcome when completed. Since there is no output schema, the description adequately covers return behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter is fully described in the schema (100% coverage). The description adds value by specifying that the case ID comes from proofstream_submit_request and provides an example format, going beyond the schema's minimal description.

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 clearly states the tool checks the status of a ProofStream verification request by case ID. It distinguishes itself from sibling tools (proofstream_submit_request and proofstream_get_pricing) by focusing solely on status retrieval.

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 description implies usage after submitting a request, but does not explicitly state when not to use it or mention alternatives. However, the sibling tool names make the context clear enough for an agent to select correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ProofStreamai/proofstream-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server