camoufox-reverse-mcp

Overview Schema Source Related Servers Discussions Admin

trace_property_access

Capture, start, stop, and query property-access traces from a live Gecko session, with summary, timeline, sequence, or search views and filters by object, kind, site, or keyword.

Instructions

Control/query the current Gecko native PropertyTracer run.

action supports capture, start, stop, query, clear, and status. Results can use summary, timeline, sequence, or search views and optional object, kind, site, and keyword filters. collect_values is a safe post-trace snapshot, not an event-time value capture.

Input Schema

TableJSON Schema

Name	Required	Default
`mode`	No	summary
`limit`	No
`action`	No	capture
`duration`	No
`bucket_ms`	No
`filter_kind`	No
`filter_site`	No
`search_query`	No
`filter_object`	No
`collect_values`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.6.0Sep 7, 2026

addedInput schema / properties / action

Added value: +{
+  "default": "capture",
+  "title": "Action",
+  "type": "string"
+}

addedInput schema / properties / filter_kind

Added value: +{
+  "title": "Filter Kind",
+  "type": "string"
+}

addedInput schema / properties / filter_site

Added value: +{
+  "title": "Filter Site",
+  "type": "string"
+}

Changed6 schema fields changedv1.1.1Jul 30, 2026
- removedInput schema / properties / filter_object / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / filter_object / default
```
Removed value: -null
```
- addedInput schema / properties / filter_object / type
```
Added value: +"string"
```
- removedInput schema / properties / search_query / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / search_query / default
```
Removed value: -null
```
- addedInput schema / properties / search_query / type
```
Added value: +"string"
```

Changed11 schema fields changedv1.0.0May 7, 2026

addedInput schema / properties / bucket_ms

Added value: +{
+  "default": 500,
+  "title": "Bucket Ms",
+  "type": "integer"
+}

addedInput schema / properties / collect_values

Added value: +{
+  "default": false,
+  "title": "Collect Values",
+  "type": "boolean"
+}

addedInput schema / properties / duration

Added value: +{
+  "default": 10,
+  "title": "Duration",
+  "type": "integer"
+}

addedInput schema / properties / filter_object

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Filter Object"
+}

addedInput schema / properties / limit

Added value: +{
+  "default": 1000,
+  "title": "Limit",
+  "type": "integer"
+}

removedInput schema / properties / max_entries

Removed value: -{
-  "default": 2000,
-  "title": "Max Entries",
-  "type": "integer"
-}

addedInput schema / properties / mode

Added value: +{
+  "default": "summary",
+  "title": "Mode",
+  "type": "string"
+}

removedInput schema / properties / persistent

Removed value: -{
-  "default": false,
-  "title": "Persistent",
-  "type": "boolean"
-}

addedInput schema / properties / search_query

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Search Query"
+}

removedInput schema / properties / targets

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "title": "Targets",
-  "type": "array"
-}

removedInput schema / required
```
Removed value: -[
-  "targets"
-]
```

First observedv0.3.0Apr 16, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The description includes a useful note that collect_values is a safe post-trace snapshot, implying no side effects for that parameter. However, it does not disclose potential effects of capture, start, stop, clear, or other actions. With no annotations, the description carries full weight but leaves room for ambiguity about state changes.

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?

The description is compact—two sentences—and efficiently communicates the core purpose, supported actions, views, filters, and a safety note. It is well-structured and front-loaded, with no extraneous information.

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

Completeness3/5

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

The description gives a reasonable overview of capabilities and a safety caveat, but it omits output format, return value details, and explicit use-case context. The sibling tool list provides some context, but the description alone is not fully self-sufficient for an agent to invoke it correctly in all scenarios.

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?

The description adds meaning to several parameters: action's possible values, filter kinds (object, kind, site, keyword), and the collect_values flag. But it leaves duration, limit, bucket_ms, and mode indirectly defined at best. The schema has zero parameter descriptions, so the description covers some but not all parameters.

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 clearly states the tool controls or queries a Gecko native PropertyTracer run and lists supported actions and result views, making its purpose evident. It does not explicitly compare with siblings, but the verb-resource pair is specific enough.

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 provides no guidance on when to use this tool versus alternative tracing or network tools. There are no conditions, scenarios, or examples mentioned that would help an agent decide between this and similar sibling tools.

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

trace_property_access

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools