Skip to main content
Glama
Sign In

Traceo

by io.github.muhamad-0
OverviewDiscussionsAdmin

Get recording thumbnail

get_thumbnail
Read-onlyIdempotent

A still image of the recorded page (the recording thumbnail).

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_thumbnail"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=true, so the safety profile is known. The description adds that the return is a 'still image' of the recorded page, which is useful but minimal. It does not describe output format, size, or retrieval behavior, leaving some behavioral ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It is appropriately sized for a simple tool, though it could be slightly more explicit by including a verb like 'retrieves'.

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?

Given the tool's simplicity (one parameter, no output schema, rich annotations), the description is adequate but not fully complete. It indicates the return is a still image but does not specify the medium (e.g., URL or binary data). For an agent to invoke correctly, this is minimally sufficient.

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 one parameter (recording) has 100% schema description coverage, explaining it accepts a share link or recording id. The description does not mention parameters at all, so it adds no meaning beyond the schema. Baseline 3 is appropriate.

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 states the resource clearly: 'a still image of the recorded page (the recording thumbnail).' It is a noun phrase rather than a verb+resource, but an agent can infer it returns a thumbnail image for a recording. Sibling tools are all different recording data types, so it is distinguishable.

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?

No when-to-use guidance is provided. It does not say when to call this versus get_frames or get_recording, nor does it mention prerequisites or exclusions. For a simple read operation this is a gap.

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