Skip to main content
Glama

open_dashboard

Mint a one-use browser URL that signs the mentee into their dashboard. kind is 'applications' (default), 'home', or 'mentorship' (pass mentorship_hash). Requires Authorization: Bearer. The link expires in 30 minutes and works once.

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

Input Schema

NameRequiredDescriptionDefault
kindNoapplications
mentorship_hashNo

Output Schema

NameRequiredDescriptionDefault
errorNo
messageNo
next_stepNo
dashboard_urlNoOne-use URL. Open in a browser. Expires in 30 minutes.
expires_in_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond annotations, it discloses that the URL is one-use, expires in 30 minutes, and requires a Bearer token. These are important operational traits for an agent that must handle a minted link securely and promptly.

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 three short sentences, front-loaded with the core action and followed by parameter and security details. Every sentence adds useful information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter tool with an output schema, the description covers the action, parameter choices, authentication, expiry, and one-use constraint. Return-value details can be omitted because an output schema exists.

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 of explaining parameters. It lists the allowed kind values, gives the default, and says mentorship_hash is passed for mentorship, though it does not explain the hash format or source.

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 uses a specific verb and resource: minting a one-use browser URL that signs a mentee into their dashboard. It clearly differentiates the operation from ordinary account or application reads, though it does not explicitly name sibling tools or state alternatives.

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?

It gives clear context for when to use the tool: when a mentee needs a browser sign-in link to a dashboard area. It also explains how to choose among the kind values, but it does not mention when not to use this tool or name alternatives.

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