Skip to main content
Glama

Managed ego-lite Browse

browse
Destructive

Manage TaskSpace session lifecycle actions and invoke allowlisted native page methods with an allowed user profile for controlled web automation.

Instructions

Run managed TaskSpace lifecycle actions and allowlisted native Page methods. Can use an allowed user Profile. Not a network or operating-system sandbox.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "browse"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
argsNo
nameNo
pageNop1
actionYes
methodNo
optionsNo
browseIdNo
profileIdNo

Output Schema

NameRequiredDescriptionDefault
pagesNo
resultNo
statusYes
spaceIdNo
browseIdNo
warningsNo
artifactIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and openWorldHint=true, so the description does not need to restate that this can alter real state. It adds meaningful context by saying an allowed user Profile may be used and that this is not a network or OS sandbox, which clarifies both identity scoping and the lack of isolation. It still leaves the semantics of actions like handoff and resume unexplained, which is important for a destructive lifecycle tool.

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 description is short and front-loaded, with no obvious filler sentences. However, the dense jargon in the first sentence reduces clarity, and the remaining sentences are sentence fragments that do not build a coherent operational picture. It is concise but under-specified rather than optimally structured.

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?

The tool is complex: 9 parameters, six lifecycle actions, open-world and destructive annotations, and an output schema. The description need not explain return values because an output schema exists, but it should explain action semantics and parameter roles. It provides only a scope boundary and a profile note, leaving too much for the agent to infer.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must carry the burden of explaining 9 parameters, including the required action enum, url, args, method, options, page, browseId, name, and profileId. It mentions only the existence of a Profile, without defining any parameter's meaning, format, or interaction. This is a severe parameter semantics gap for a multi-action tool.

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 identifies a verb ('Run') and a broad resource ('managed TaskSpace lifecycle actions and allowlisted native Page methods'), so it is more than a tautology. However, 'TaskSpace', 'ego-lite', and 'native Page methods' are opaque domain terms, and the description does not explicitly distinguish this tool from siblings such as browse_evaluate, fetch, or crawl. An agent can infer it manages page lifecycle, but only after reading the action enum.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The statement 'Not a network or operating-system sandbox' gives a useful negative boundary, but it does not tell the agent when to select browse over browse_evaluate, fetch, or crawl.

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