← WebMCP Directory

traces.ribdsp.com

traces.ribdsp.com

live Unverified (seed import) Developer Tools 17 tools imperative implementation

A session replay player an AI agent can interrogate through WebMCP: bisect the timeline, read the DOM at any moment, and file a verifiable bug report.

First seen 2026-11-05 · Last seen 2026-11-05 · Source: webmcp.com

Answer 9 · Act 7 · Transact 1 · Score: Not yet scored

Tool inspector

propose_report

act imperative

Propose a bug report and wait for the human to approve or edit it. Reproduction steps are validated against the recorded events, and any step no event supports is marked unverified rather than quietly dropped.

Input schema

PropertyTypeRequiredDescription
title string yes One line naming the bug, e.g. "Province dropdown is empty, so checkout cannot be completed". At most 120 characters.
summary string no A short paragraph on what happened and why it matters. At most 600 characters.
steps array yes The reproduction steps, in order, at most 12. Pass an empty array to have the page reconstruct them from the recorded events instead of writing them yourself.
expected string no What should have happened, e.g. "The dropdown lists the provinces for the selected country."
actual string no What did happen, e.g. "The dropdown opened with no options and the Pay button stayed disabled."
rootCause string yes Your explanation of the cause, in one or two sentences, based on what you found in the recording.
evidence array no The moments that back the report, at most 10. Each becomes a clickable timestamp in the report.
ticket string no Only when retrying a call that previously returned status "pending". Do not invent one — pass back exactly the ticket you were given, e.g. "ask-1a2b3c4d".
Raw JSON schema
{
  "type": "object",
  "properties": {
    "title": {
      "type": "string",
      "description": "One line naming the bug, e.g. \"Province dropdown is empty, so checkout cannot be completed\". At most 120 characters."
    },
    "summary": {
      "type": "string",
      "description": "A short paragraph on what happened and why it matters. At most 600 characters."
    },
    "steps": {
      "type": "array",
      "description": "The reproduction steps, in order, at most 12. Pass an empty array to have the page reconstruct them from the recorded events instead of writing them yourself.",
      "items": {
        "type": "object",
        "properties": {
          "text": {
            "type": "string",
            "description": "One action, e.g. \"Open the province dropdown\". At most 200 characters."
          },
          "atMs": {
            "type": "number",
            "description": "When the recording shows this step happening, in milliseconds from the start, e.g. 28412. Give it whenever you know it: a step with no timestamp cannot be matched against the recorded events and is shown to the human as unverified."
          }
        },
        "required": [
          "text"
        ],
        "additionalProperties": false
      }
    },
    "expected": {
      "type": "string",
      "description": "What should have happened, e.g. \"The dropdown lists the provinces for the selected country.\""
    },
    "actual": {
      "type": "string",
      "description": "What did happen, e.g. \"The dropdown opened with no options and the Pay button stayed disabled.\""
    },
    "rootCause": {
      "type": "string",
      "description": "Your explanation of the cause, in one or two sentences, based on what you found in the recording."
    },
    "evidence": {
      "type": "array",
      "description": "The moments that back the report, at most 10. Each becomes a clickable timestamp in the report.",
      "items": {
        "type": "object",
        "properties": {
          "atMs": {
            "type": "number",
            "description": "When it happened, in milliseconds from the start of the recording, e.g. 28412."
          },
          "note": {
            "type": "string",
            "description": "What that moment shows, in a few words, e.g. \"GET /provinces returned 500\"."
          }
        },
        "required": [
          "atMs"
        ],
        "additionalProperties": false
      }
    },
    "ticket": {
      "type": "string",
      "description": "Only when retrying a call that previously returned status \"pending\". Do not invent one — pass back exactly the ticket you were given, e.g. \"ask-1a2b3c4d\"."
    }
  },
  "required": [
    "title",
    "steps",
    "rootCause"
  ],
  "additionalProperties": false
}

Similar websites

morphus.myles4miles.chatgpt.site

morphus.myles4miles.chatgpt.site

Morphus is an AI-native workspace for designing worlds and generating playable game experiences.

live Unverified Developer Tools Transact tools
154 tools A23 / Act124 / T7 Not yet scored Seen 2026-11-05
list_nodes get_scene_settings get_node_details get_terrain_state get_forest_state
Inspect tools
damnpdfs.com

damnpdfs.com

Install the DamnPDFs Codex plugin, pair a browser workspace and use PDF, image and file tools from your coding agent. Includes setup and privacy limits.

live Unverified Developer Tools Transact tools
81 tools A3 / Act77 / T1 Not yet scored Seen 2026-11-05
scan_to_pdf workflow merge_pdf alternate_mix_pdf compress_pdf
Inspect tools
insignifi4nt.github.io

insignifi4nt.github.io

broCAD/M: local-first CAD and CAM for parametric design, wire EDM planning, simulation and controller export.

live Unverified Developer Tools Transact tools
80 tools A29 / Act49 / T2 Not yet scored Seen 2026-11-05
edm_inspect_approach edm_describe_edits edm_get_context edm_list_projects edm_get_project
Inspect tools
cabinet.varera.studio

cabinet.varera.studio

The Cartographer's Cabinet

live Unverified Developer Tools Transact tools
64 tools A10 / Act50 / T4 Not yet scored Seen 2026-11-05
inspect_daylight inspect_cartographers_project list_project_hierarchy inspect_open_map search_project_objects
Inspect tools

Related on Influzer