Skip to main content
Glama

Kubeez

open_gallery

Read-onlyIdempotent

Scope: none. Deep-link to the user's generations history page. Use when the user asks 'show me my last X' or wants to browse / share past generations visually rather than via get_generations JSON. Optional status filter is appended as a query param. Returns { url, summary }. On hosts supporting MCP Apps this also renders the thumbnails inline.

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

Input Schema

NameRequiredDescriptionDefault
statusNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile needs no restating. The description adds real context beyond that: it returns `{ url, summary }`, the status filter is applied as a query param, and on MCP Apps hosts thumbnails render inline. Only 'Scope: none' is left unexplained.

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?

Front-loaded with scope, then purpose, then trigger, then the sibling alternative, then return shape and host-specific behavior. No filler sentences; each clause contributes distinct routing or behavioral information.

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 single-optional-param deep-link tool with annotations and an output schema, coverage is nearly complete: return shape, filter handling, and host-dependent rendering are all disclosed. The leading 'Scope: none' is opaque — it is unclear whether it refers to workspace scoping or something else, and that is the one unresolved point.

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 description coverage is 0%, so the description carries the burden; it explains that `status` is optional and is appended as a query param, which is more than the bare enum conveys. It does not spell out enum semantics (e.g. that empty means all statuses), which the default `""` implies but never states.

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?

States a specific verb and resource ('Deep-link to the user's generations history page') and immediately contrasts it with the sibling `get_generations` by output modality (visual browse vs JSON). An agent can route between the two without inspecting either schema.

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

Usage Guidelines5/5

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

Gives a concrete trigger ('show me my last X'), a use case (browse / share past generations), and an explicit alternative plus the condition that selects it ('rather than via `get_generations` JSON'). The when-and-when-not is fully resolved in the description.

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