Skip to main content
Glama
bnookala

MCP Cookie Server

by bnookala

reset_cookies

Clear all accumulated cookies to restore the initial state for testing scenarios in the MCP Cookie Server's reinforcement system.

Instructions

Reset the cookie count back to zero (for testing purposes)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The switch case handler for the 'reset_cookies' tool. It calls cookieStorage.reset() to reset the collected cookies count and returns a confirmation text message.
    case "reset_cookies": {
      cookieStorage.reset();
      
      return {
        content: [
          {
            type: "text",
            text: "🔄 Cookie count has been reset to 0. Time to start earning cookies again!",
          },
        ],
      };
    }
  • src/index.ts:177-184 (registration)
    Registration of the 'reset_cookies' tool in the ListToolsRequestSchema handler. Includes the tool name, description, and empty input schema (no parameters required).
    {
      name: "reset_cookies",
      description: "Reset the cookie count back to zero (for testing purposes)",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Helper method 'reset()' in the CookieStorage class that resets only the collected cookies counter to zero, preserving the jar cookies. Called by the tool handler.
    reset(): void {
      this.collectedCookies = 0;
      // Note: Don't reset jar cookies, only collected cookies
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the tool's purpose and testing context but lacks details on behavioral traits such as whether this requires special permissions, if it's reversible, or what happens to existing data. The description is accurate but minimal in behavioral disclosure.

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 action ('reset the cookie count back to zero') and adds necessary context ('for testing purposes') without any wasted words. Every part of the sentence earns its place.

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 adequate but minimal. It covers the purpose and usage context but lacks details on behavioral aspects like side effects or return values, which could be helpful for an agent 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 adds value by explaining the tool's effect ('reset... back to zero') and context ('for testing purposes'), which goes beyond the empty schema, justifying a score above the baseline of 3.

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 specific action ('reset'), the target resource ('cookie count'), and the outcome ('back to zero'), with explicit mention of the testing context. It distinguishes from siblings like 'add_cookies_to_jar' or 'check_cookies' by focusing on resetting rather than modifying or querying.

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 explicitly states 'for testing purposes', providing clear context for when to use this tool. However, it does not specify when not to use it or mention alternatives like 'give_cookie' for non-testing scenarios, which prevents a perfect score.

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