Skip to main content
Glama

dejo_profile

Switch between or list separate signed-in browser profiles, creating one by name on first use, so customer, vendor, and admin sessions stay signed in side by side.

Instructions

Website profiles and roles: customer, vendor, admin. A profile is a whole signed-in browser; several stay signed in side by side. With a name: switch to it (made on first use). Without: list them. Trails are shared by every profile.

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

Input Schema

NameRequiredDescriptionDefault
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it says profiles are separate signed-in browsers, several can stay signed in side by side, a named profile is created on first use, and trails are shared across profiles. It still omits details such as what switching changes for subsequent calls and whether any return value is produced.

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?

The description is short, front-loaded, and free of filler. Its telegraphic phrasing is efficient, though lines like 'Trails are shared by every profile' are slightly cryptic without broader context.

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 simple tool with one optional parameter and no output schema or annotations, the definition covers the essential modes, profile creation on first use, and shared trails. It is largely complete, though it could clarify what switching or listing returns and how switching affects later tool calls.

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 single optional parameter has 0% schema description coverage, but the description compensates by explaining that a supplied name switches to that profile and creates it if needed, while omission lists profiles. It does not describe naming format or constraints.

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 defines the resource as website profiles/roles and explains the two behaviors: switching when a name is supplied and listing when omitted. It is specific about the operation, though it does not explicitly distinguish this tool from siblings such as dejo_login.

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?

It gives explicit parameter-driven usage: use a name to switch profile and omit it to list profiles. However, it provides no guidance on when to choose this tool over related tools like dejo_login or dejo_manage, so alternative routing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.