Skip to main content
Glama
Sign In
Cat Burglar

Cat Burglar

by DrMkdaddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Browser status

status
Read-only

Reports the active engine, URL, tabs, capture buffers, resolved config, and available engines to verify the current browser session state and environment.

Instructions

Report the active engine, URL, tabs, capture buffers, resolved config, and which engines are available on this machine.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The readOnlyHint=true annotation already establishes this is a safe, non-mutating call, and the description aligns with it rather than contradicting it. It adds real value by enumerating the payload contents, which matters because there is no output schema. It does not describe response shape or format beyond the field list, keeping it out of 5 territory.

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?

A single front-loaded sentence with the verb first and the reported fields following as a tight list. There is no filler, hedging, or restatement of the tool name.

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 is the only source of return-value information, and it does supply a field inventory. Some terms such as "capture buffers" and "resolved config" remain underspecified, so an agent knows what categories come back but not their exact shape.

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, so the baseline is 4 and there is no schema semantics the description could add or should compensate for. Nothing in the description conflicts with the empty input object.

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?

A specific verb ("Report") plus an explicit enumeration of the resources reported: active engine, URL, tabs, capture buffers, resolved config, and available engines. That distinguishes it clearly from action siblings like click, navigate, or tabs. It stops short of naming a sibling it is not, so it sits at 4 rather than 5.

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?

The description never states when an agent should call this instead of other introspection tools such as console, network, memory, or snapshot, nor does it give preconditions. The phrase "which engines are available on this machine" hints at a discovery use case, but the agent must infer that.

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