Skip to main content
Glama

cookies

Read-only

Lists the HTTP cookie headers a browser would send to a tab's current page, including HttpOnly values, to inspect session and state.

Instructions

List the cookies the browser would send to the tab's current page, including httpOnly ones.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, so the description's job is lighter. It adds real value by disclosing that httpOnly cookies are included, which tells the agent this surfaces data JavaScript cannot read, and that results are limited to cookies applicable to the current page. It omits whether browser cookie permissions or an extension grant are required.

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?

One sentence, front-loaded with the verb and resource, with the two most decision-relevant qualifiers (page scoping, httpOnly) inline. Nothing is wasted and no clause needs re-reading.

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

Completeness4/5

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

For a zero-required-parameter read tool with full schema coverage and annotations, this is nearly complete. The only minor gap is the absence of any hint about return shape (cookie names, values, domains), which matters somewhat since no output schema exists.

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

Parameters3/5

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

Schema description coverage is 100% and the single `tab` parameter already documents its format and that it is optional when only one tab is shared. The description adds nothing about the tab handle, so the baseline 3 applies.

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?

States a specific verb (List) and resource (cookies) and narrows the scope precisely: only the cookies the browser would send to the tab's current page, explicitly including httpOnly ones. An agent immediately knows this is a scoped read of the active page's cookie jar rather than a general storage dump; no sibling overlaps, so no differentiation is needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated — reading auth/session cookies for the current page. It does not say when to prefer this over other inspection tools (e.g., run_js reading document.cookie) or mention any exclusions such as cross-domain or non-matching cookies beyond the sentence's scope clause.

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