Skip to main content
Glama

browser_api

Read the local CUA compatibility API and its documented limitations to understand which browser automation actions are supported.

Instructions

Read the local cua compatibility API and its limitations.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. "Read" implies a non-mutating operation, but nothing is said about what the response contains, how large it is, whether it reflects a live browser state, or whether it requires an open session — all of which matter for a diagnostics-style call.

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

Conciseness4/5

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

A single short sentence with no padding, and the operative verb is front-loaded. It is efficient, though its brevity comes partly from omitting substance rather than from tight editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-output-schema tool the description is the only source of information, and it leaves the key questions open: what "cua" means, what the API document covers, and how the reported limitations should influence subsequent tool selection. That is a significant gap for a tool whose whole purpose is to inform other calls.

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?

The tool takes zero parameters and the schema is an empty object, so there is no parameter meaning to convey. Baseline 4 applies; the description does not need to explain arguments here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description has a verb ("Read") and an object ("the local cua compatibility API and its limitations"), so the general shape is clear. But "cua compatibility API" is unexplained jargon, and the description gives no hint of what that API actually exposes, leaving the agent unable to distinguish it confidently from siblings such as browser_capabilities or browser_capabilities-adjacent tools.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus browser_capabilities or any other sibling, and no prerequisites or exclusions. The phrase "and its limitations" weakly implies it is for checking compatibility constraints, but the agent must infer that entirely.

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