Skip to main content
Glama
Sign In
arc-cdp-mcp

arc-cdp-mcp

by chmodami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Screenshot

arc_screenshot

Capture a tab's current visual state as a PNG image to inspect page rendering. Supports full-page capture via optional parameter.

Instructions

Captura a aba como PNG. Use para ver o estado visual da página.

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

Input Schema

NameRequiredDescriptionDefault
tabIdNoAba alvo. Omita para usar a aba própria ativa (nunca uma aba do usuário).
fullPageNoPágina inteira em vez da viewport.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of explaining behavior. It accurately describes the capture action and PNG output, but does not mention whether the tool has side effects, permissions, or limitations beyond the visible state.

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 very concise: two short sentences that state the action and the intended use. There is no redundant or filler content.

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?

For a simple capture tool, the description and schema together are mostly complete. It specifies the output format (PNG) and the purpose, though it could mention more about the returned image details or whether any page interaction occurs.

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?

The schema already provides full descriptions for both parameters (tabId and fullPage), so the tool description adds no additional parameter-level meaning. Since schema coverage is 100%, the baseline score 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?

The description clearly states the tool captures the active tab as a PNG and is used to see the page's visual state. This distinguishes it from sibling tools like arc_read_page, which are more text/DOM-focused.

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 explicit guidance on when to use the tool: 'Use para ver o estado visual da página.' It does not explicitly contrast with alternatives, but the purpose is clear enough for an agent to select it appropriately.

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