Skip to main content
Glama

studio_describe

Read-only

Discover AI creation workflows, RP/1 command schemas, and craft guidance on demand without opening a project.

Instructions

按需发现AI创作流程、RP/1、命令schema与craft指导。topic:command用name或names;fields/operation/surface仅用于topic:node。节点用name+fields查询;源码许可与真实生效验证分开登记。无需打开工程。

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_describe"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
namesNo
topicNo
fieldsNo
intentNo
guideIdNo
surfaceNo
platformNo
operationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

B3.1/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 structurally. The description adds a genuinely useful behavioral note, '无需打开工程' (no need to open a project), which tells the agent this works without prior state. The remaining sentence about source licensing and 'real effective verification' being registered separately is too cryptic to convey concrete behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and there is no filler, but the telegraphic phrasing and unexplained abbreviations ('RP/1', '分开登记') cost clarity. Several clauses assume context the agent does not have, so brevity comes at the expense of comprehension.

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?

Reconsidering: for a 9-parameter read-only discovery tool with no output schema, the description plus the enum-rich schema give the agent enough to invoke it, and 'no need to open a project' answers the main contextual unknown. The silent intent, guideId, and platform parameters are the main residual gap, keeping it below a 5.

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 0%, so the description carries the full burden for 9 parameters, and it only partially does so. It explains the role of name, names, fields, operation, and surface relative to topics, but intent, guideId, and platform are never mentioned anywhere. Half compensation against a total schema gap lands at a minimum-viable 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and a set of resources ('discover AI creation workflows, RP/1, command schema and craft guidance'), which is more than a restatement of the name. However, two of the six enum topics ('design', 'node') are barely or not covered in prose, so the agent must read the schema enum to learn the full scope. There is no differentiation from overlapping siblings such as studio_query_nodes, studio_operations, or studio_get_context.

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?

It gives real routing rules: 'topic:command uses name or names' and 'fields/operation/surface only apply to topic:node', plus 'nodes are queried with name+fields'. That is useful conditional guidance for parameter combinations. It stops short of saying when to prefer this tool over the sibling discovery tools, and gives no exclusions.

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