Skip to main content
Glama
Sign In

Remote Desktop Commander

by app.desktopcommander
OverviewDiscussionsAdmin

get_recent_tool_calls

Read-only
                    Get recent local tool call history with arguments and outputs.
                    Returns a chronological list of recent calls loaded from the local history file.
                    
                    Useful for:
                    - Onboarding new chats about work already done
                    - Recovering context after chat history loss
                    - Debugging tool call sequences
                    
                    Note: Does not track its own calls or track_ui_event.
                    History is persisted locally in tool-history.jsonl, keeps up to the last 1000
                    calls in memory, and trims older on-disk history. Stored outputs over 4 KiB
                    are replaced with an omission marker.
                    
                    This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.

Input Schema

NameRequiredDescriptionDefault
sinceNo
deviceIdNoThe ID of the device to run this tool on (from list_devices). Required when more than one device is online; may be omitted when only one device is connected.
toolNameNo
maxResultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Adds substantial context beyond the readOnlyHint/openWorldHint annotations: persistence path (tool-history.jsonl), a 1000-call in-memory cap, on-disk trimming, 4 KiB output omission markers, and self-call exclusion. These are exactly the retention and completeness caveats an agent needs before trusting the results.

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?

Front-loaded with the core action and well-organized into purpose, use cases, and behavioral notes. The trailing 'DC: ... / use Desktop Commander to ...' boilerplate adds no selection or invocation value.

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?

With no output schema, the description does explain the return (chronological list with arguments and outputs) and the truncation behavior. For a read-only query tool with annotations covering safety, the only real hole is the undocumented filter parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% — just deviceId is documented. The description says nothing about 'since', 'toolName', or 'maxResults' (default 50, max 1000), so an agent must infer that filtering by time and tool name is even possible. It does not compensate for the coverage gap at all.

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?

States a specific verb and resource: 'Get recent local tool call history with arguments and outputs,' plus clarifies it is loaded from a local history file. 'Local' implicitly separates it from the sibling list_remote_tool_calls, though it never names that sibling.

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?

Gives three concrete 'Useful for' scenarios (onboarding, context recovery, debugging) and a coverage caveat that it excludes its own calls and track_ui_event. It stops short of naming alternatives or stating when not to use it, so it lands at clear-context rather than explicit routing.

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

All Remote Desktop Commander 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