Skip to main content
Glama

Open the Ubi research workspace

open_research_app
Read-onlyIdempotent

Request the research workspace, optionally focused on a topic or feature. Returns authorized tools and requests host display; successful rendering is unverified. Display status is requested, not confirmed open.

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

Input Schema

NameRequiredDescriptionDefault
focusNo

Output Schema

NameRequiredDescriptionDefault
modeYes
focusYes
capabilitiesYes
display_statusYes
display_verifiedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, but the description adds genuinely new context: it returns authorized tools and, crucially, that successful rendering is unverified and display status is only requested rather than confirmed. That caveat directly prevents an agent from assuming the UI opened.

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 short, with the key limitation stated up front. The last two clauses are somewhat redundant ('successful rendering is unverified' / 'requested, not confirmed open'), so it is tight but not maximally economical.

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?

A low-complexity, zero-required-parameter tool with an output schema and strong annotations; the description supplies the missing behavioral caveat about unverified display and the returned tools. Nothing essential for correct invocation appears absent, though a note on what the focus string influences would complete it.

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% for the single 'focus' parameter, so the description must compensate. It does explain that focus is optional and takes a topic or feature, but gives no format, length, or example values.

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 specific verb and resource ('Request the research workspace') plus an optional focus, which is enough to separate it from the account/model retrieval siblings. It stops short of explaining what the 'research workspace' actually is, so the agent knows the action but not the payload.

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?

Usage is only implied: the agent can infer it should call this when it wants the research workspace or the authorized tools, and the 'focus' framing hints at narrowing. There is no explicit when-to-use, when-not, or named alternative.

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