Skip to main content
Glama
Sign In
imagine-mcp

imagine-mcp

by n24q02m
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Config Open Relay

config__open_relay

Retrieve the relay configuration URL for imagine-mcp and open it in the user's browser when possible, returning the URL, launch status, and current state.

Instructions

Get the relay configuration URL for imagine-mcp, opening it in the user's browser when possible. Returns the relay URL, whether the browser launched, and the current status.

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": "config__open_relay"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the browser may be opened and lists returned fields, but it does not cover prerequisites, authentication, or failure behavior.

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?

The description is a single, well-structured sentence that front-loads the primary action and adds the side effect. Every phrase is relevant and there is no wasted text.

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?

Given the simple zero-parameter interface and the existence of an output schema, the description provides enough context for the tool's purpose and side effect. It does not need to explain return values in depth, and the lack of explicit usage alternatives is a minor gap.

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?

The tool has zero parameters and the schema is empty, so there are no parameter semantics to document. The baseline for a zero-parameter tool is 4.

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 clearly states the specific action and resource: getting the relay configuration URL for imagine-mcp. It does not explicitly differentiate from the sibling config tool, but the relay-specific scope is evident from the tool name and description.

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 implied by the relay configuration context, but the description offers no explicit guidance on when to use this versus config, help, or other siblings. The 'when possible' phrase describes browser behavior, not tool selection.

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