Skip to main content
Glama
Prooflie

Proofly MCP Integration

by Prooflie

check-session-status

Check the status of a deepfake analysis session to determine if an image authenticity assessment is complete.

Instructions

Check the status of a deepfake analysis session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionUuidYesSession UUID to check status for.
formatNoOutput format.text

Implementation Reference

  • The handler function that implements the core logic of the 'check-session-status' tool. It fetches the status from the Proofly API using the sessionUuid, formats the output in JSON or text, and handles errors like 404 for unknown sessions.
    async handleCheckSessionStatus(params) {
      logInfo("Handling check-session-status with params:", params);
      const { sessionUuid, format = 'text' } = params;
    
      if (!sessionUuid) {
        throw new McpError(ErrorCode.InvalidParams, "Missing sessionUuid parameter");
      }
    
      try {
        logInfo(`Fetching status for UUID ${sessionUuid}`);
        const statusResp = await axios.get(`${PROOFLY_CONFIG.baseUrl}/api/${sessionUuid}/status`);
        const statusData = statusResp.data;
        logInfo(`Status data for ${sessionUuid}:`, statusData);
    
        if (format === 'json') {
          return { content: [{ type: "text", text: JSON.stringify(statusData, null, 2) }] }; 
        } else {
          // Simple text representation of the status
          let output = `**Session Status for ${sessionUuid}:**\n`;
          output += `* Status: ${statusData.status || 'N/A'}\n`;
          if (statusData.message) {
            output += `* Message: ${statusData.message}\n`;
          }
          if (statusData.result) {
              output += `* Result available: Yes\n`;
          }
          return { content: [{ type: "text", text: output }] };
        }
      } catch (error) {
        logError("Error in handleCheckSessionStatus:", error.message);
        if (error.response) {
          logError("Error response data:", error.response.data);
          logError("Error response status:", error.response.status);
        }
        // If API returns 404 for unknown UUID, this may be expected
        if (error.response && error.response.status === 404) {
          throw new McpError(ErrorCode.NotFound, `Session with UUID ${sessionUuid} not found.`);
        }
        throw new McpError(ErrorCode.ServerError, `Failed to check session status: ${error.message}`);
      }
    }
  • The input schema definition for the 'check-session-status' tool, specifying required sessionUuid and optional format parameter.
    {
      name: "check-session-status",
      description: "Check the status of a deepfake analysis session.",
      inputSchema: {
        type: "object",
        properties: {
          sessionUuid: { type: "string", description: "Session UUID to check status for." },
          format: { type: "string", enum: ["json", "text"], default: "text", description: "Output format." },
        },
        required: ["sessionUuid"],
      },
    },
  • server.js:236-237 (registration)
    Registers the list of tools including 'check-session-status' via the ListToolsRequestSchema handler.
    this.mcpServer.setRequestHandler(ListToolsRequestSchema, async () => ({ tools }));
  • server.js:247-248 (registration)
    Registers the handler dispatch for 'check-session-status' in the CallToolRequestSchema switch statement.
    case "check-session-status":
      return await this.handleCheckSessionStatus(args);
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention whether this is read-only (implied but not explicit), rate limits, authentication needs, or what the status response includes (e.g., pending, completed, error).

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every word earning its place.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete for a tool that likely returns status details. It doesn't explain what status information is provided (e.g., progress, results, errors), leaving significant gaps in understanding the tool's behavior and output.

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%, so the schema fully documents both parameters (sessionUuid and format). The description adds no additional meaning beyond what the schema provides, such as explaining session UUID context or format implications, meeting the baseline for high coverage.

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 clearly states the action ('Check the status') and resource ('deepfake analysis session'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'analyze' or 'analyze-image' which might also involve session status, so it doesn't reach the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'analyze' or 'analyze-image'. It doesn't mention prerequisites (e.g., needing a session UUID from a previous analysis) or exclusions, leaving usage context unclear.

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/Prooflie/mcp'

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