Skip to main content
Glama

Choose a linked desktop

writ_devices
Idempotent

The user's linked Writ desktops: list, use (scope this connection to one: runs, browsers, personas and monitors then target it), clear, monitors, datasets.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "writ_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNolist (default) | use | clear | monitors | datasets.
deviceNouse: the desktop's agent_id or name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"list (default) | use | clear | monitors (that desktop's monitors) | datasets (what its exposed workflows collected)."New value: +"list (default) | use | clear | monitors | datasets."
    • changedInput schema / properties / device / description
      Previous value: -"use: the desktop's agent_id (or its exact name) from list."New value: +"use: the desktop's agent_id or name."
    • removedInput schema / required
      Removed value: -[]
  2. 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=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context that 'use' re-scopes the whole connection and affects runs, browsers, personas and monitors. It does not explain what 'clear' actually reverts or whether scoping persists across calls, so it adds moderate rather than rich context.

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?

A single compact sentence with the resource front-loaded and the actions enumerated as a list. No wasted prose, though the fragment style and dense parenthesis on 'use' slightly hurt readability.

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?

For a five-action tool with no output schema, the description defines only 'use' in any depth; 'list', 'clear', 'monitors' and 'datasets' are left as bare labels, so an agent cannot tell what each returns or mutates. The schema enum names are fairly self-descriptive, which keeps this at a minimum-viable 3 rather than lower.

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%: the action enum and the device field are both documented in the schema. The description restates the action list and clarifies the effect of 'use', which lightly reinforces semantics but adds little beyond the schema, making the baseline 3 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 names the resource (the user's linked Writ desktops) and enumerates the five operations it multiplexes (list, use, clear, monitors, datasets), so an agent knows what it deals with. It does not explicitly differentiate itself from siblings like writ_personas or writ_browser_use, which is the main thing keeping it below 5.

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

Usage Guidelines3/5

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

The parenthetical on 'use' implies the operational context (scoping a connection to one desktop for runs, browsers, personas and monitors), which is real usage guidance. But there is no explicit when-to-use/when-not, no mention of ordering (e.g., list before use), and no routing away from alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.