Skip to main content
Glama

studio_operations

Query, list, or cancel long-running Studio operations by project using an ID or requestKey, and read completed results. State persists across MCP disconnects or server restarts to avoid repeated work.

Instructions

按工程持久查询、列出或取消长操作。可按id或原requestKey核对,MCP断连/服务重开不重做。cancel分别返回请求确认与实际停止;includeResult读取完成结果,过期结果移除提交建议。

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

Input Schema

NameRequiredDescriptionDefault
idNo
urlNo
portNo
limitNo
actionNo
projectDirNo
requestKeyNo
includeResultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses meaningful behavior: results persist per project across reconnects, cancel returns two distinct signals (request acknowledgement vs actual stop), includeResult fetches completed output, and expired results trigger a removal/submission suggestion. This is substantial extra context for a tool that mixes read and cancel actions under a non-read-only annotation.

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?

The core capability is front-loaded in the first clause, followed by reconciliation semantics and cancel/includeResult behavior. Sentences are dense but each carries information; no filler or repetition.

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 eight parameters at 0% schema coverage and no output schema, the description should explain more. It covers the key cross-cutting behavior well but leaves url/port/limit unexplained and does not clarify which parameters apply to which action.

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 must carry parameter meaning, and it only partly does: it explains id, requestKey, action (get/list/cancel), includeResult, and the project scoping implied by projectDir. The url, port, and limit parameters receive no explanation, leaving several of the eight parameters undocumented.

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 a specific verb triad and resource: persistently query, list, or cancel long-running operations scoped to a project ('按工程持久查询、列出或取消长操作'). This clearly separates it from the design/export siblings, though it does not name any particular sibling as an alternative.

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?

Implicit usage context is present: the tool is for reconciling an operation after an MCP disconnect or service restart without redoing work ('MCP断连/服务重开不重做'), and lookups can be keyed by id or original requestKey. However, there is no explicit statement of when to prefer cancel vs get vs list, nor any when-not guidance.

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