Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Set Cookies

set_cookies

Injects ad hoc authentication cookies into a specified tab to enable temporary access to protected pages without changing stored credentials.

Instructions

Set cookies (each: name/value/domain required). For ad-hoc auth injection.

Ex: set_cookies('t0', [{'name':'sid','value':'abc','domain':'.x.com','secure':True}]) → {"set":1}

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": {
      "tab_id": "<tab_id>",
      "cookies": "<cookies>"
    },
    "name": "set_cookies"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYes
cookiesYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden and it does not meet it. It never says whether cookies persist across navigations, whether existing cookies with the same name/domain are overwritten, whether httpOnly/secure semantics apply, or what permissions/state are needed — only a terse return shape example is given.

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 tight sentences: purpose and constraint first, then a compact concrete example. The example with its '{"set":1}' return earns its space; nothing is padded.

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?

An output schema exists and the example covers the return value, so that is not a gap. But for a mutation tool with zero annotations, the description omits the tab_id parameter, persistence/overwrite behavior, and any indication of effect scope — an agent could call it correctly only by guessing.

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 0%, and the description only documents half the job well: it specifies that each cookie requires name/value/domain and shows a full example including 'secure'. The required tab_id parameter is never mentioned anywhere, leaving a real gap.

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 and resource ('Set cookies') and adds the qualifier 'For ad-hoc auth injection,' which separates it from session-oriented siblings like session_load or warm_session without naming them. The parenthetical constraint on cookie fields further pins down what the tool accepts.

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?

'For ad-hoc auth injection' implies the use case, but it never states when to prefer this over session_load, warm_session, or set_extra_headers, nor any preconditions (e.g., that a live tab must exist). The alternative-routing that would earn a 4-5 is absent.

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