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

arc-cdp-mcp

by chmodami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Ler página

arc_read_page

Reads the visible page text and lists interactive elements with stable refs, enabling reliable clicks and typing without inventing CSS selectors.

Instructions

Devolve o texto visível da página e a lista de elementos interativos, cada um com um ref estável. Use os refs em arc_click e arc_type em vez de inventar seletores CSS.

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_read_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoAba alvo. Omita para usar a aba própria ativa (nunca uma aba do usuário).
maxCharsNoCorte do texto (padrão 8000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

The description implies a read-only operation through the verb 'Devolve' (returns) and the tool name, but does not explicitly state that no modifications occur. Given the absence of annotations, a slight clarity gain could be made, but it is still largely transparent.

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 concise and well-structured, conveying the core functionality and usage guidance in two sentences without unnecessary fluff.

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?

It clearly describes the primary output (text and interactive elements with refs) and how to use it, but does not detail the exact structure of the returned data (e.g., JSON format). Still, it is sufficient for the agent to understand what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters have descriptive comments: tabId explains it targets a specific tab and defaults to the active tab (never the user's), and maxChars explains it truncates text with a default of 8000. This fully clarifies the parameter meanings.

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 returns visible page text and interactive elements with stable refs, and explicitly links to sibling tools arc_click and arc_type, distinguishing its purpose from those tools.

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?

It provides explicit guidance to use the returned refs in arc_click and arc_type instead of inventing CSS selectors, which tells the agent exactly when and how to use this tool compared to 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