Skip to main content
Glama
Sign In
Tap

Tap

by LeonTing1010
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

inspect

Read-only

Retrieve current page metadata, DOM, accessibility tree, element details, or network traffic. Choose a target to get the specific data.

Instructions

Inspect the current page. Use target to choose what to inspect: page (url/title/meta), dom (HTML structure), a11y (accessibility tree), element (single element detail, requires selector), network (captured traffic — auto-starts capture on first call, dumps on subsequent). Default: page.

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": "inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodiesNoInclude response bodies (target=network only)
targetNoWhat to inspectpage
selectorNoCSS selector (required for target=element, optional for target=dom to scope)
url_filterNoFilter network entries by URL substring (target=network only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.15.14
  2. Removedv0.15.8
  3. Addedv0.1.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate read-only and non-destructive behavior. The description adds useful behavioral detail for the 'network' target, specifying auto-start and dump behavior. No contradictions.

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 two concise sentences with front-loaded purpose. Every part adds value, no redundancy.

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?

The description covers main targets and network behavior, but lacks details on output format. Given no output schema, this is a minor gap. Overall, it provides a solid understanding for an agent.

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?

Schema covers all parameters with descriptions. The tool description adds extra meaning by summarizing what each target inspects and noting that 'element' requires a selector, enhancing understanding beyond the 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 clearly states the tool inspects the current page and lists target options. However, it does not differentiate from the sibling tool 'forge_inspect', which may serve a similar purpose.

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?

The description provides clear context for each target option and explains default behavior. It does not explicitly state when not to use the tool or mention alternatives, but the guidance for target selection is sufficient.

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