Skip to main content
Glama
Sign In
chromaphore-mcp

chromaphore-mcp

Official
by nodriver-project
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List the page

observe
Read-only

Waits for a page to settle and lists its elements with IDs, roles, names, values, states, open overlays, and live-region announcements so you can inspect and act on the current UI.

Instructions

Waits for the page to settle and lists it: one line per element with its id (a12), role, name, value, states and where it is; what is open on top (a dialog, a menu); and live-region announcements. Elements in view that can be acted on carry the [color] of their outline on the screenshot view shows.

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

Input Schema

NameRequiredDescriptionDefault
scopeNoall: also list elements behind what is open on top, which a click cannot reach.
offscreenNoElements outside the view: none, summary (default: what can be acted on or is named), or full.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

The readOnlyHint annotation is consistent with a pure observation tool, so the bar for behavioral disclosure is lower. The description still adds real context beyond annotations: it blocks until the page settles, reports what is stacked on top (dialogs, menus), includes live-region announcements, and color-codes actionable elements to match outlines in the screenshot view. It does not discuss cost, timeout, or volume limits, so it falls short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core content is front-loaded and dense with useful detail, but the second sentence is grammatically garbled ('carry the [color] of their outline on the screenshot view shows'), which forces the reader to re-parse it. The single sprawling first sentence would read better split by output section.

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?

With no output schema, the description must carry the return-format burden, and it does: it enumerates the per-element fields, the overlay section, live-region announcements, and the actionability color cue. The enum parameters are documented in the schema. Only the interaction between 'scope: all' and the overlay section is left implicit.

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?

Both parameters are enums with 100% schema description coverage, including the default for offscreen, so the schema already carries the semantics. The description only indirectly gestures at scope via 'what is open on top' and adds no format or interaction detail for the two enum values. Baseline 3 is appropriate when the schema does the heavy lifting.

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 gives a concrete verb and resource: waits for the page to settle and lists every element with id, role, name, value, states, and position, plus overlays and live-region announcements. An agent gets a precise picture of what the tool returns. It does not explicitly contrast itself with siblings such as view or screenshot, which keeps it from a 5.

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

Usage Guidelines3/5

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

Usage is only implied: 'waits for the page to settle' signals this is a post-action observation call, and the reference to the screenshot view hints at a relationship with the screenshot tool. There is no explicit when-to-use vs when-not-to-use guidance and no named alternative for cheaper or non-settling snapshots.

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