Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

Record Marker

record_marker
Destructive

Drops a named marker into the active recording's timeline. t_ms is elapsed ms since recording start. Provide bounds (global points, top-left) to zoom toward an element, or omit for full-frame. note becomes a caption source. Returns no_active_session if nothing is recording.

Input Schema

NameRequiredDescriptionDefault
nameYesMarker name, e.g. open_tray, act2_calendar_create.
noteNoFree text → caption source.
boundsNoOptional {x,y,w,h} global points to zoom toward.
confirmNoIgnored; kept for older clients.
session_idNoAccepted and IGNORED: v1 records one session at a time, so a marker always lands on the active recording. It is here so echoing back the session_id from screen_record_start is not an error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to drop the marker; it is stamped at that call. Without it the call returns a preview and adds nothing."New value: +"Ignored; kept for older clients."
  2. Changed1 schema field changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Must be true to drop the marker; it is stamped at that call. Without it the call returns a preview and adds nothing.",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / session_id / description
      Added value: +"Accepted and IGNORED: v1 records one session at a time, so a marker always lands on the active recording. It is here so echoing back the session_id from screen_record_start is not an error."
  4. Changed1 schema field changed
    • removedInput schema / properties / session_id / description
      Removed value: -"Accepted and IGNORED: v1 records one session at a time, so a marker always lands on the active recording. It is here so echoing back the session_id from screen_record_start is not an error."
  5. Changed1 schema field changed
    • addedInput schema / properties / session_id / description
      Added value: +"Accepted and IGNORED: v1 records one session at a time, so a marker always lands on the active recording. It is here so echoing back the session_id from screen_record_start is not an error."
  6. Added

TDQS

A4.7/5.0
Behavior5/5

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

It adds critical operational details beyond the annotations. It defines the temporal parameter t_ms, explains the complex zooming behavior of the bounds parameter (zoom toward element vs. full-frame), and specifies the failure condition when no active session is found.

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 highly dense and efficient. Every clause addresses a vital piece of information—what it does, how the timeline works, how zoom works, and what happens on error.

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

Completeness5/5

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

Given the complexity of interacting with a timeline and providing spatial hints, the description is highly complete. It covers the primary function, key parameter behavior, intended output use, and failure state.

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?

Since schema coverage is 100%, the baseline is high. The description adds value by defining the meaning of t_ms and, crucially, explaining the functional difference between omitting bounds vs. providing bounds (zoom vs. full-frame).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Drops a named marker') and the precise resource it operates on ('active recording's timeline'). It immediately distinguishes itself by focusing on timeline marking, setting it apart from general note or task creation tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides excellent context by stating that the note becomes a caption source, defining its functional use case. While it doesn't explicitly name siblings to avoid, the specific focus on timeline marking makes the usage context clear.

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

All Local MCP 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