Skip to main content
Glama
Sign In

Traceo

by io.github.muhamad-0
OverviewDiscussionsAdmin

Get console logs

get_console_logs
Read-onlyIdempotent

Browser console output captured during the recording, one line per entry. Secrets are redacted.

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": {
      "recording": "<recording>"
    },
    "name": "get_console_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoOnly these levels (default all).
limitNoMax lines to return.
cursorNoPagination cursor from a previous call.
searchNoCase-insensitive substring filter on the message.
recordingYesTraceo share link (e.g. https://www.traceo.dev/abc123...) or recording id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and a closed-world profile, so safety is covered. The description adds two genuinely useful behavioral facts: results are one line per entry and secrets are redacted, which sets expectations about output content. It does not mention ordering or how pagination interacts with limits, so it stays at an adequate level.

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?

Two short sentences with zero padding; the core identification comes first and the redaction caveat follows as useful qualification. Nothing could be trimmed without losing information.

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?

For a five-parameter read tool with a fully documented schema and no output schema, the description supplies what the schema cannot: the per-entry line format and the redaction guarantee. Only log ordering and truncation behavior are left unstated, which is a minor residual gap.

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?

Schema description coverage is 100%, with every parameter (level, limit, cursor, search, recording) documented inline, so the schema carries the semantics. The description adds no filtering or format detail beyond that, which is the expected baseline when the schema is complete.

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 names a specific resource (“browser console output captured during the recording”) with a format note (“one line per entry”), which clearly separates it from sibling readers like get_network_requests or get_user_actions. The retrieval verb is implicit rather than stated, but the scope is unmistakable.

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 agent must infer from the purpose sentence alone that this is for debugging console errors rather than network or UI activity.

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

All Traceo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources