Skip to main content
Glama
bnookala

MCP Cookie Server

by bnookala

cookie_jar_status

Check cookie jar capacity and remaining space to monitor available treats in the MCP Cookie Server's reinforcement system.

Instructions

Check the current status of the cookie jar including capacity and remaining space

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the cookie_jar_status tool that calls getJarStatus on the CookieStorage instance and formats a detailed status message based on availability.
    case "cookie_jar_status": {
      const status = cookieStorage.getJarStatus();
      
      let statusText = `🏺 **Cookie Jar Status:**\n\n`;
      statusText += `**Collected Cookies:** ${status.collected}\n`;
      statusText += `**Available in Jar:** ${status.available}\n`;
      
      if (status.isEmpty) {
        statusText += `**Status:** 🔴 EMPTY\n\n`;
        statusText += `The cookie jar is completely empty! No more cookies can be awarded until a user refills it.`;
      } else if (status.isLow) {
        statusText += `**Status:** ⚠️ LOW\n\n`;
        statusText += `Warning: Only ${status.available} cookie${status.available === 1 ? '' : 's'} left! Each cookie is now extremely precious.`;
      } else {
        statusText += `**Status:** 🟢 STOCKED\n\n`;
        statusText += `The jar has ${status.available} cookie${status.available === 1 ? '' : 's'} available for earning through quality work.`;
      }
      
      return {
        content: [
          {
            type: "text",
            text: statusText,
          },
        ],
      };
    }
  • src/index.ts:204-211 (registration)
    Registration of the cookie_jar_status tool in the ListToolsRequestSchema handler, defining its name, description, and empty input schema.
    {
      name: "cookie_jar_status",
      description: "Check the current status of the cookie jar including capacity and remaining space",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema for the cookie_jar_status tool, which requires no parameters.
    inputSchema: {
      type: "object",
      properties: {},
    },
  • Core helper method in CookieStorage class that returns the status object (collected, available, isEmpty, isLow) used directly by the tool handler.
    getJarStatus(): { collected: number; available: number; isEmpty: boolean; isLow: boolean } {
      const isEmpty = this.jarCookies <= 0;
      const isLow = this.jarCookies > 0 && this.jarCookies <= 2;
      
      return {
        collected: this.collectedCookies,
        available: this.jarCookies,
        isEmpty,
        isLow
      };
    }
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 indicates a read-only operation ('Check') but does not specify whether this requires permissions, how frequently it can be called, or what happens if the jar is empty. 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 that front-loads the core purpose without unnecessary details. Every word earns its place by specifying the action, target, and key attributes, making it easy to parse and understand quickly.

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 (zero parameters, no output schema, no annotations), the description is adequate but incomplete. It explains what the tool does but lacks context on usage scenarios, behavioral constraints, or output format, which could hinder an agent's ability to use it effectively in complex environments.

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 tool has zero parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description adds no parameter information, which is acceptable given the baseline for zero parameters is 4, as it doesn't need to compensate for any schema gaps.

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 ('Check') and resource ('cookie jar'), specifying what information is retrieved ('current status', 'capacity and remaining space'). It distinguishes itself from siblings like 'check_cookies' by focusing on jar status rather than cookie contents, though the distinction could be more explicit.

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 'check_cookies' or 'add_cookies_to_jar'. It implies usage for monitoring jar status but offers no explicit context, prerequisites, or exclusions, leaving the agent to infer appropriate scenarios.

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/bnookala/mcp-cookiejar'

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