Skip to main content
Glama
dqhieu
by dqhieu

get-total-processed-files

Retrieve the total number of files processed by Compresto's compression app. This MCP tool provides real-time statistics for monitoring file processing activity and usage metrics.

Instructions

Get total processed files of Compresto

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that fetches landing page data from Supabase API and returns the total number of processed (compressed) videos.
    async () => {
      const url = `${API_BASE}/v1/getLandingPageData`;
      const response = await makeSupabaseRequest<LandingPageDataResponse>(url);
      
      if (!response) {
        return {
          content: [
            {
              type: "text",
              text: "Failed to fetch user data"
            }
          ],
          isError: true
        };
      }
      
      return {
        content: [
          {
            type: "text",
            text: `Processed ${response.data.totalCompressedVideos} files`
          }
        ]
      };
    },
  • src/index.ts:78-107 (registration)
    Registration of the 'get-total-processed-files' tool using server.tool, including name, description, empty input schema, and inline handler.
    server.tool(
      "get-total-processed-files",
      "Get total processed files of Compresto",
      {},
      async () => {
        const url = `${API_BASE}/v1/getLandingPageData`;
        const response = await makeSupabaseRequest<LandingPageDataResponse>(url);
        
        if (!response) {
          return {
            content: [
              {
                type: "text",
                text: "Failed to fetch user data"
              }
            ],
            isError: true
          };
        }
        
        return {
          content: [
            {
              type: "text",
              text: `Processed ${response.data.totalCompressedVideos} files`
            }
          ]
        };
      },
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't reveal any behavioral traits such as whether it's read-only, requires authentication, has rate limits, or what the return format might be. This is a significant gap for a tool with zero annotation coverage.

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 with no wasted words. It's front-loaded with the core purpose, making it highly concise and well-structured.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states the purpose but lacks behavioral context and usage guidance, making it incomplete for optimal agent understanding despite the low complexity.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, earning a baseline score of 4 for tools with no parameters.

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 ('Get') and resource ('total processed files of Compresto'), providing a specific purpose. However, it doesn't differentiate from sibling tools like 'get-total-size-reduced' or 'get-total-users', which would require explicit comparison to earn a 5.

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 the sibling tools. There's no mention of context, prerequisites, or exclusions, leaving usage entirely implicit.

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

Related 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/dqhieu/compresto-mcp'

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