Skip to main content
Glama
yfe404

proxy-mcp

by yfe404
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

interceptor_browser_get_cookie

Retrieve a specific cookie's full value by its cookie ID from a browser session, with an optional max length to keep output bounded.

Instructions

Get one cookie by cookie_id with full value (subject to a hard cap to keep output bounded).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cookie_idYescookie_id from interceptor_browser_list_cookies
target_idYesTarget ID from interceptor_browser_launch
value_max_charsNoMax characters for cookie value (default: 20000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.3
    • changedInput schema / properties / target_id / description
      Previous value: -"Target ID from interceptor_browser_launch or interceptor_camoufox_launch"New value: +"Target ID from interceptor_browser_launch"
  2. Changed1 schema field changedv3.3.1
    • changedInput schema / properties / target_id / description
      Previous value: -"Target ID from interceptor_browser_launch"New value: +"Target ID from interceptor_browser_launch or interceptor_camoufox_launch"
  3. Addedv2.3.0

TDQS

A4/5.0
Behavior3/5

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

No annotations, so description must disclose behavior. Mentions 'full value' and 'hard cap', but lacks details like truncation behavior, auth requirements, or rate limits.

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?

Single sentence, front-loaded with verb and resource. No extraneous words.

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?

No output schema; description mentions 'full value' but not structure. Adequate for a simple retrieval tool, but could specify return format or error handling.

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 has 100% description coverage. Description adds little beyond restating the key parameters (cookie_id) and the cap concept. Baseline 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?

Clearly states action ('Get'), resource ('one cookie'), identifier ('by cookie_id'), and constraint ('hard cap'). Distinct from sibling tools like list_cookies.

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?

Implicitly suggests usage after list_cookies (cookie_id from there). Mentions hard cap for output bounding, but no explicit when-not or alternatives.

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