Skip to main content
Glama

studio_get_context

Read-only

Reads the current free-canvas session state—revisions, content hash, pages, components, tokens, fonts, and recovery summary—so agents can verify and resume design edits.

Instructions

读取自由画布当前会话状态(appliedRevision、durableRevision、renderedRevision、contentHash、页面、组件、令牌、字体与恢复摘要)。

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

Input Schema

NameRequiredDescriptionDefault
urlNo
portNo
verboseNo
maxBytesNo
includeDocNo
projectDirNo
includeSceneNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing the shape of what is returned (revision triples, content hash, recovery summary), but says nothing about side effects on the canvas, freshness/consistency guarantees, or cost of the call.

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 front-loaded sentence with no filler. The parenthetical field list is dense internal jargon but is the useful part, so it earns its space; it could be trimmed slightly.

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?

With no output schema, the description does well to enumerate return fields, and annotations cover safety. However, seven entirely undocumented parameters, including ones that presumably gate whether document or scene payloads are included, is a meaningful completeness gap for a tool that returns canvas state.

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 seven parameters (url, port, verbose, maxBytes, includeDoc, projectDir, includeScene), and the description explains none of them. It only lists return fields, so an agent gets no help deciding what includeDoc/includeScene or maxBytes (capped at 400000) do.

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 states a specific verb (读取) and a specific resource (自由画布当前会话状态), then enumerates the concrete state fields returned (appliedRevision, durableRevision, renderedRevision, contentHash, pages, components, tokens, fonts, recovery summary). This is clearly a session/revision-state read rather than a design-content read like studio_get_design_context, though it never names a sibling to make that contrast explicit.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus alternatives such as studio_get_design_context or studio_describe, and no prerequisites or exclusions. The usage is only implied by the phrase 'current session state', leaving the agent to infer the trigger condition.

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

Deploy Server

Other Tools