Skip to main content
Glama
Sign In
Web Inspector MCP

Web Inspector MCP

by antonzherdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

confirm_output

Read-only

Retrieve the complete output of a large result previously shown as a preview, using a one-time token to avoid resending original parameters.

Instructions

Return full output for a previously previewed large result using a one-time token. Use when a tool responded with a preview + token. Safer than resending original parameters.

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": {
      "token": "<token>",
      "reason": "<reason>"
    },
    "name": "confirm_output"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesOne-time token obtained from a tool's preview response
reasonYesExplain why the full output is needed and how it will be used. This helps the user understand whether the action is reasonable and necessary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, indicating no side effects. Description aligns by stating it returns output and uses a one-time token. However, it could mention what happens if the token is invalid or expires, which would add further transparency.

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?

Two sentences, no redundant information. Every sentence serves a purpose: stating the action and providing usage guidance. Front-loaded with the main verb.

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?

The description lacks details about the return format or content of the 'full output'. Since there is no output schema, the description should specify what the output looks like or at least give a hint. This gap reduces completeness.

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 coverage is 100% and descriptions for both parameters are already clear. The description does not add additional meaning beyond what the schema provides, so baseline of 3 is appropriate.

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?

Description clearly states the action: returning full output using a one-time token from a preview. It specifies the trigger condition and distinguishes from siblings by mentioning preview/token context, which none of the sibling tools address.

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

Usage Guidelines5/5

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

Explicitly instructs when to use: when a tool responded with a preview + token. Also provides a rationale ('Safer than resending original parameters'), helping the agent decide between 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