bc-rig

browser_observe

Read-onlyIdempotent

Read the current browser state from an active Business Central session. Compact mode returns stable references; full mode provides detailed data with query support.

Instructions

Read the selected project browser. Call browser_session first. Compact returns stable @b refs; full is costly.

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

Input Schema

Name	Required	Description	Default
`mode`	No		compact
`limit`	No
`query`	No	Required for query; filters compact controls too
`since`	No	Return only unchanged when revision matches
`offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0Jul 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already provide readOnly=true and idempotent=true. Description adds that compact returns stable @b refs and full is costly, plus the prerequisite of browser_session. Could mention error behavior if prerequisite not met.

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 concise sentences with no superfluous text. Starts with purpose, then usage guidance. Every sentence adds value.

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 read tool with good annotations and no output schema, the description is nearly complete. Tells prerequisite, mode differences. Lacks explanation of 'selected project browser' and potential errors.

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 only 40% (only query and since have descriptions). Description links compact mode to stable refs, but does not explain limit, offset, or query beyond schema. Some added value but insufficient to compensate for low coverage.

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 it reads the selected project browser, distinguishing from action tools like browser_act and browser_screenshot. Mentions compact and full modes, with specific behavior for compact (stable @b refs).

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?

Explicitly states 'Call browser_session first' as a prerequisite. Contrasts compact vs full ('Compact returns stable @b refs; full is costly'), guiding mode selection. Does not exclude alternatives like mobile_observe.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server