Skip to main content
Glama

Kubeez

open_studio

Read-onlyIdempotent

Scope: none. Return a deep-link the user can open to land in the Kubeez studio with their context prefilled. Use when the agent has done the planning + first generation and the user wants to continue iterating in the UI (richer controls, side-by-side compare, drag-and-drop refs). Optional: prompt, model, aspect_ratio — get appended as query params. Returns { url, summary }. Just hand the url to the user; do NOT try to render the page.

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
modelNo
promptNo
aspect_ratioNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered; the description still adds real behavioral guidance beyond them — 'Just hand the url to the user; do NOT try to render the page' and the optional-params-become-query-params mechanic. It does not mention URL lifetime or any auth/login requirement, which is the remaining gap.

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?

Front-loaded and dense: scope, purpose, when-to-use, parameter behavior, return shape, and a usage warning, all in four short sentences. The leading fragment 'Scope: none.' is unclear on its own and slightly out of register with the rest, but nothing is padding.

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?

For a simple three-optional-param deep-link tool with an output schema already present, this covers the essentials: what it produces, how params are applied, and how the caller should handle the result. Only minor context is missing — whether the URL expires or requires the user to be signed in.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the load, and it names all three parameters (prompt, model, aspect_ratio) and explains their effect: appended as query params. It does not say what value formats are valid (model ids, aspect ratio syntax) or that they are all optional, but the core semantics are supplied where the schema gives nothing.

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?

States a concrete verb and artifact: 'Return a deep-link the user can open to land in the Kubeez studio with their context prefilled.' That is specific enough to distinguish it from generation tools, though it never names its nearest analogues (open_gallery, open_pricing) to draw the boundary explicitly.

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 a clear triggering condition: use after the agent has done the planning + first generation and the user wants to continue iterating in the UI, with the reason spelled out (richer controls, side-by-side compare, drag-and-drop refs). It offers no explicit 'do not use when' clause or named alternative, so it falls short of a 5.

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