Skip to main content
Glama

Open in studio

open_in_studio
Destructive

Hand this project from automatic Quick processing to the full Studio editor when the user requests manual correction. Stops Quick automation; this is an intentional change, not just a preview link.

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": {
      "project_id": "<project_id>",
      "expected_revision": "<expected_revision>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "open_in_studio"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
idempotency_keyYes
expected_revisionYes

Output Schema

NameRequiredDescriptionDefault
errorNo
mediaNo
quoteNo
stageNo
statusNo
visualNo
projectNo
progressNo
can_retryNo
can_startNo
demo_modeNo
can_cancelNo
project_idNo
studio_urlNo
can_handoffNo
lyrics_sourceNo
preview_readyNo
visual_sourceNo
visual_warningNo
command_versionNo
project_revisionNo
can_replace_lyricsNo
can_update_visualsNo
visual_preferencesNo
needs_lyrics_reviewNo
lyrics_search_outcomeNo
lyrics_search_providerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedOutput schema / oneOf
      Previous value: -[
      -  {
      -    "required": [
      -      "project_id",
      -      "project_revision",
      -      "command_version",
      -      "status",
      -      "stage",
      -      "quote",
      -      "can_start",
      -      "can_retry",
      -      "can_cancel",
      -      "can_handoff",
      -      "preview_ready",
      -      "needs_lyrics_review",
      -      "progress",
      -      "visual_preferences",
      -      "visual",
      -      "visual_source",
      -      "visual_warning",
      -      "error",
      -      "lyrics_source",
      -      "lyrics_search_outcome",
      -      "lyrics_search_provider",
      -      "demo_mode",
      -      "project",
      -      "studio_url",
      -      "media"
      -    ]
      -  },
      -  {
      -    "maxProperties": 1,
      -    "properties": {
      -      "error": {
      -        "additionalProperties": true,
      -        "maxProperties": 32,
      -        "properties": {
      -          "code": {
      -            "maxLength": 120,
      -            "minLength": 1,
      -            "type": "string"
      -          },
      -          "message": {
      -            "maxLength": 2000,
      -            "minLength": 1,
      -            "type": "string"
      -          },
      -          "retryable": {
      -            "type": "boolean"
      -          }
      -        },
      -        "required": [
      -          "code",
      -          "message",
      -          "retryable"
      -        ],
      -        "type": "object"
      -      }
      -    },
      -    "required": [
      -      "error"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "required": [
      +      "project_id",
      +      "project_revision",
      +      "command_version",
      +      "status",
      +      "stage",
      +      "quote",
      +      "can_start",
      +      "can_retry",
      +      "can_cancel",
      +      "can_handoff",
      +      "preview_ready",
      +      "needs_lyrics_review",
      +      "can_replace_lyrics",
      +      "can_update_visuals",
      +      "progress",
      +      "visual_preferences",
      +      "visual",
      +      "visual_source",
      +      "visual_warning",
      +      "error",
      +      "lyrics_source",
      +      "lyrics_search_outcome",
      +      "lyrics_search_provider",
      +      "demo_mode",
      +      "project",
      +      "studio_url",
      +      "media"
      +    ]
      +  },
      +  {
      +    "maxProperties": 1,
      +    "properties": {
      +      "error": {
      +        "additionalProperties": true,
      +        "maxProperties": 32,
      +        "properties": {
      +          "code": {
      +            "maxLength": 120,
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "message": {
      +            "maxLength": 2000,
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "retryable": {
      +            "type": "boolean"
      +          }
      +        },
      +        "required": [
      +          "code",
      +          "message",
      +          "retryable"
      +        ],
      +        "type": "object"
      +      }
      +    },
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / can_replace_lyrics
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / can_update_visuals
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / project / properties / has_lyrics
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / project / required
      Previous value: -[
      -  "id",
      -  "title",
      -  "artist",
      -  "duration_seconds",
      -  "revision",
      -  "has_export",
      -  "export_status",
      -  "visual_settings"
      -]New value: +[
      +  "id",
      +  "title",
      +  "artist",
      +  "duration_seconds",
      +  "revision",
      +  "has_export",
      +  "has_lyrics",
      +  "export_status",
      +  "visual_settings"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds the concrete consequence ('Stops Quick automation') and frames it as intentional, which is the key behavioral fact. It stops short of saying whether the switch is reversible or how a revision conflict is surfaced.

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?

Two tight sentences with the mutation stated first and the disambiguation second; no filler. Every clause carries information an agent needs.

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?

The output schema covers return values, so nothing is owed there. But for a destructive state-transition command that requires expected_revision and an idempotency key, the missing notes on conflict handling and post-switch state leave real operational gaps.

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 0% across three required parameters, so the description carries the full burden and supplies nothing about project_id, expected_revision, or idempotency_key. The presence of a required idempotency key is especially notable given idempotentHint=false, and the description does not clarify that tension or explain the optimistic-concurrency contract.

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 state transition ('Hand this project from automatic Quick processing to the full Studio editor') rather than restating the name. It also preempts a likely misread by saying this is 'not just a preview link', which separates it from a read-only open/preview action.

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 an explicit trigger: 'when the user requests manual correction'. That is a clear when-to-use condition, but there is no when-not guidance and no named alternative for agents that only want to view the project.

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.

Resources