Skip to main content
Glama
Sign In
Cat Burglar

Cat Burglar

by DrMkdaddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Cookies

cookies

Get, set, or clear browser cookie state for the current context; limit retrieval to specific URLs when needed.

Instructions

Get, set, or clear cookies for the current browser context. get can be limited to URLs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "cookies"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsNoFor get: only cookies sent to these URLs.
actionYes
cookiesNoFor set: cookie objects (name, value, domain, path, expires, sameSite…).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations supply only readOnlyHint=false, so the description carries the burden of disclosing behavior. It does not say that `clear` removes cookies (destructive and irreversible), whether `clear` respects the urls filter or wipes the entire context, or whether `set` overwrites an existing cookie of the same name/domain/path. These are material behaviors for a mixed read/write tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core capability and no filler; the action set is stated immediately. It is efficient, though the second sentence is arguably redundant with the schema rather than an addition.

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?

This is a mutating tool (set/clear) with only a single weak annotation and no output schema, and 67% parameter coverage. The description omits what `clear` affects, whether `set` replaces or adds, and what the get response contains, leaving an agent likely to call `clear` with unintended blast radius.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single sentence about `urls` restates what the schema already documents ('For get: only cookies sent to these URLs'), so it adds no meaning beyond structured data. With 67% schema coverage and an action enum that the schema already constrains, the description contributes nothing new about `cookies` payload shape or the scoping semantics of `clear`.

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 gives three specific verbs (get, set, clear) bound to a concrete resource (cookies) scoped to the current browser context, which is enough for an agent to know exactly what the tool does. It stops short of 5 because it never distinguishes itself from the sibling `storage` tool, which an agent could easily confuse with cookie access.

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?

There is no when-to-use framing at all: no mention of preferring `storage` for localStorage/sessionStorage, no prerequisites (e.g., an open page/context), and no guidance on which action is appropriate in which situation beyond the bare verb list. The agent must infer usage entirely from the action enum.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools