Skip to main content
Glama
JoodasCode

SlopWatch MCP Server

slopwatch_status

Retrieve current slop score and statistics to track AI system accountability by comparing promised versus delivered implementations.

Instructions

Get current slop score and statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
random_stringYesDummy parameter for no-parameter tools

Implementation Reference

  • The handleStatus method implements the core logic for the slopwatch_status tool, calculating accuracy from claims and verification results and returning a simple status message.
    async handleStatus(args) {
      const totalClaims = this.claims.size;
      const verifiedClaims = this.verificationResults.filter(r => r.isVerified).length;
      const accuracy = totalClaims > 0 ? Math.round((verifiedClaims / totalClaims) * 100) : 100;
    
      return {
        content: [
          {
            type: 'text',
            text: `Accuracy: ${accuracy}% (${verifiedClaims}/${totalClaims})`
          }
        ]
      };
    }
  • The getStatus function implements the slopwatch_status tool handler, providing detailed server status including recent verification history if requested.
    async function getStatus(args: any, claims: Map<string, any>, verificationResults: any[]) {
      const { detailed = false } = args || {};
      
      const totalClaims = claims.size;
      const verifiedClaims = verificationResults.filter(r => r.isVerified).length;
      const failedClaims = verificationResults.filter(r => !r.isVerified).length;
      const accuracy = totalClaims === 0 ? 100 : Math.round((verifiedClaims / totalClaims) * 100);
    
      let output = `šŸ”„ SlopWatch Server Status\n\n`;
      output += `šŸ“Š Total Claims: ${totalClaims}\n`;
      output += `āœ… Verified: ${verifiedClaims}\n`;
      output += `āŒ Failed: ${failedClaims}\n`;
      output += `šŸŽÆ AI Accuracy: ${accuracy}%\n\n`;
    
      if (detailed && verificationResults.length > 0) {
        output += `šŸ“‹ Recent Verification History:\n`;
        verificationResults.slice(-5).forEach((result, i) => {
          const status = result.isVerified ? 'āœ…' : 'āŒ';
          output += `   ${status} "${result.claim}" (${result.confidence}%)\n`;
        });
      }
    
      output += `\nšŸ’” How to use:\n`;
      output += `1. AI calls slopwatch_claim("what I'm implementing", ["file1.js"], "js")\n`;
      output += `2. AI makes the changes\n`;
      output += `3. AI calls slopwatch_verify(claimId)\n`;
      output += `4. Get instant lie detection results!\n`;
    
      return {
        content: [
          {
            type: 'text',
            text: output
          }
        ]
      };
  • Registration of the slopwatch_status tool in the ListTools response, defining name, description, and input schema.
    {
      name: 'slopwatch_status',
      description: 'Get current slop score and statistics',
      inputSchema: {
        type: 'object',
        properties: {
          random_string: {
            type: 'string',
            description: 'Dummy parameter for no-parameter tools'
          }
        },
        required: ['random_string']
      }
    },
  • src/index.ts:88-100 (registration)
    Registration of the slopwatch_status tool in the ListTools response for the stateless server, including optional detailed parameter.
    {
      name: 'slopwatch_status',
      description: 'šŸ“Š Get current SlopWatch status and recent verification results',
      inputSchema: {
        type: 'object',
        properties: {
          detailed: {
            type: 'boolean',
            description: 'Show detailed verification history',
          }
        },
      },
    }
  • Input schema definition for slopwatch_status tool requiring a dummy random_string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        random_string: {
          type: 'string',
          description: 'Dummy parameter for no-parameter tools'
        }
      },
      required: ['random_string']
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 implies a read-only operation ('Get'), but doesn't specify whether this requires authentication, has rate limits, returns real-time or cached data, or what format the statistics include. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 ('Get current slop score and statistics'), making it easy to parse quickly. Every word earns its place in this concise formulation.

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 the lack of annotations and output schema, the description is incomplete for a tool that presumably returns data. It doesn't explain what 'slop score' means, what statistics are included, or the format of the response. For a read operation with no structured output documentation, the description should provide more context to be fully helpful.

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 100% description coverage, documenting the single parameter as a 'Dummy parameter for no-parameter tools.' The description doesn't add any parameter details beyond this, but since the schema fully covers the parameter and it's a dummy placeholder, the baseline is high. A score of 4 reflects that the description doesn't detract from the schema's clarity for this simple case.

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 tool's purpose with a specific verb ('Get') and resource ('current slop score and statistics'), making it immediately understandable. However, it doesn't explicitly differentiate this read-only status tool from its sibling tools (slopwatch_claim_and_verify and slopwatch_setup_rules), which appear to involve write operations, so it falls short of a perfect 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 its siblings or in what context. It lacks any mention of prerequisites, alternatives, or exclusions, leaving the agent to infer usage based on tool names alone.

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/JoodasCode/SlopWatch'

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