Skip to main content
Glama

intercept_off

Idempotent

Disable request interception to stop filtering HTTP traffic and restore normal network operations.

Instructions

Disable request interception.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for 'intercept.off' tool - disables network request interception by sending Fetch.disable command via Chrome debugger protocol
    case 'intercept.off': {
      try { await chrome.debugger.sendCommand({ tabId }, 'Fetch.disable') } catch {}
      scheduleDetach(tabId)
      return {}
    }
  • Tool registration in capabilities - 'intercept.off' is listed in the supports array returned by the capabilities method
    case 'capabilities':
      return {
        runtime: 'extension', version: '0.6.5',
        supports: [
          'eval', 'pointer', 'keyboard', 'nav', 'wait', 'screenshot', 'cookies', 'storage',
          'click', 'type', 'fill', 'hover', 'scroll', 'pressKey', 'select',
          'fetch', 'find', 'download', 'waitFor', 'waitForNetwork', 'ssrState', 'copyAll',
          'upload', 'dialog', 'extract',
          'tab.new', 'tab.list', 'tab.close',
          'inspect.page', 'inspect.networkStart', 'inspect.networkDump', 'inspect.networkStop',
          'intercept.on', 'intercept.off'
        ]
      }
  • Related handler for 'intercept.on' tool - enables network request interception with URL patterns
    case 'intercept.on': {
      await ensureDebugger(tabId)
      const patterns = (params.patterns || ['*']).map(p => ({ urlPattern: p }))
      await chrome.debugger.sendCommand({ tabId }, 'Fetch.enable', { patterns })
      const session2 = debuggerSessions.get(tabId)
      if (session2?.detachTimer) { clearTimeout(session2.detachTimer); session2.detachTimer = null }
      return {}
    }
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, establishing safety. The description adds domain context by specifying 'request interception' as the target, but lacks behavioral details such as whether pending requests are affected or if this clears interception logs.

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 extremely concise at three words with no redundant phrases. The critical action ('Disable') is front-loaded, making it immediately scannable.

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?

For a simple state-toggle tool with no output schema and strong annotations, the description is minimally sufficient. However, it misses the opportunity to clarify the relationship with 'intercept_on' or explain the scope of the disabled interception (e.g., per-tab vs global).

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 tool has zero parameters, which establishes a baseline score of 4. The description appropriately requires no additional parameter explanation given the empty input schema.

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 uses a specific verb ('Disable') and resource ('request interception'), making the immediate purpose clear. However, it does not explicitly distinguish from sibling 'intercept_on' or clarify that this is the counterpart action to stop interception.

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?

The description provides no guidance on when to use this tool versus its sibling 'intercept_on', nor does it mention prerequisites (e.g., that interception should be active first) or when to prefer this over other inspection tools.

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/LeonTing1010/tap'

If you have feedback or need assistance with the MCP directory API, please join our Discord server