Skip to main content
Glama

Start a Johari window

start_johari
Read-only

Get the link to a free online Johari window: the person picks 6 words that describe them, sends one link to friends or colleagues who pick 6 words for them, and sees their open area, blind spot and hidden area (from 3 answers) with a short AI explanation. A light, playful alternative to a full 360.

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

Input Schema

NameRequiredDescriptionDefault
languageNoen, fr, de or es; default en

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower; the description goes beyond them by disclosing the whole operating model — the link is shared with friends/colleagues, results depend on 3 answers, and an AI explanation is attached. It leaves out link persistence/expiry and whether anything is stored, which are minor gaps for a link-generating tool.

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?

A single sentence with the action front-loaded, followed by the minimum flow context needed to understand the output. Every clause earns its place — the 6-words/3-answers detail explains the result the agent will report back.

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 zero-required-parameter tool with no output schema, the description is sufficient: it explains what the returned link is for and what the end user will see. It could be tightened with a note on whether the link expires or is one-per-user, but nothing essential to invoking the tool is missing.

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?

There is only one optional parameter (language, enum en/fr/de/es) and schema description coverage is 100%, so the schema already documents it fully including the default. The description adds no information about the language parameter at all, which matches the baseline 3 for a fully-covered schema.

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 ('Get the link to a free online Johari window') and then explains the exact mechanics: pick 6 words, share one link, recipients pick 6 words, results show open/blind/hidden areas from 3 answers. It also positions itself against the sibling by calling itself 'a light, playful alternative to a full 360', so an agent can distinguish it from start_360 without opening a schema.

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?

The closing clause 'a light, playful alternative to a full 360' gives a clear selection cue against start_360. It stops short of explicit when/when-not conditions (e.g. 'use this when the user wants a quick icebreaker rather than a full review') and says nothing about check_360_status or compare_with, so it's clear context rather than explicit routing.

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