Skip to main content
Glama

open_studio

Launch the Copperflow visual editor for PCB work: reuses an existing Studio session or starts one and opens it in the browser, returning the address so a person can watch the agent's changes live.

Instructions

Open the Studio, the visual editor, for the person: reuses this project's running Studio or starts one, and opens it in their browser. Call it when the person asks to open copperflow, the editor or the board, or wants to watch. Give them the address it returns, to them only.

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": "open_studio"
  }
}

Input Schema

NameRequiredDescriptionDefault
openNoOpen the person's browser; default true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only say it is non-read-only, non-destructive and not open-world; the description adds the genuinely useful behavior: it may reuse an already-running instance instead of starting a new one, it opens the user's browser, and it returns an address. The privacy instruction ('to them only') is a real operational constraint not captured anywhere in structured fields. It stops short of saying what happens on failure or whether repeated calls spawn multiple sessions.

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?

Three short sentences ordered by importance: what it does, when to call it, then the follow-up obligation about the returned address. The phrasing 'for the person' and 'or wants to watch' is slightly loose, but nothing is redundant.

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?

There is no output schema, yet the description covers the key return fact — it yields an address that must be relayed to the requesting user only. Combined with the reuse-or-start behavior and browser opening, this is nearly everything an agent needs to invoke and report back correctly; only failure/lifecycle behavior is absent.

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% and the single `open` parameter is already documented as 'Open the person's browser; default true'. The description implies the browser-opening behavior but adds no format, default, or interaction detail beyond the schema, so baseline 3 applies.

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?

Names a specific verb (open) and resource (the Studio, defined inline as the visual editor), and states the underlying mechanic: it reuses this project's running Studio or starts one. An agent immediately knows this launches a UI session rather than editing anything.

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 concrete trigger phrases — the person asking to open copperflow, the editor or the board, or wanting to watch — which maps well onto natural user requests. It does not state when not to use it or name any alternative, but no sibling appears to overlap, so the guidance is sufficient in practice.

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