Skip to main content
Glama

use_account

Idempotent

Selects this session's account role, lists roles when called without arguments, and logs in to or creates the chosen role's account; a role used by another session cannot be selected.

Instructions

Selects this session's account (role). Called with no arguments, it lists the roles for this folder (description and whether in use). With role, it logs in to that role's account (creating it if needed). The same role maps to the same account after restarts. A role used by another session cannot be selected.

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

Input Schema

NameRequiredDescriptionDefault
areaNoAccount area: local (default) or connection (a connection account that talks to other PCs — only while connected to a communication server). A session uses one area only.
roleNoRole name (e.g. planner, builder). Omit to only list roles.
descriptionNoRole description (profile). Visible to other sessions and the admin app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / area
      Added value: +{
      +  "description": "Account area: local (default) or connection (a connection account that talks to other PCs — only while connected to a communication server). A session uses one area only.",
      +  "enum": [
      +    "local",
      +    "connection"
      +  ],
      +  "type": "string"
      +}
  2. First observedv2.1.1

TDQS

A4.1/5.0
Behavior5/5

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

Annotations say readOnlyHint=false and idempotentHint=true but nothing more. The description adds the material behavior: selecting also logs in, creates the account if it does not exist, the role-to-account mapping survives restarts, and cross-session locking prevents selecting an in-use role. That is exactly the context an agent needs before a state-changing call.

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?

Four short sentences, front-loaded with the core action and immediately followed by the dual calling modes and the constraints. Nothing is repeated and no sentence is padding.

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?

With no output schema, the description usefully sketches what the listing mode returns (description and whether in use) and covers persistence and concurrency. It does not say what a successful login returns or how failures surface, a minor gap given the available annotations and full schema coverage.

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 coverage is 100%, so every parameter (including area and its enum) is already documented in the schema. The description reinforces the role-omission case but adds no syntax, defaults, or area semantics beyond what the schema provides, so the baseline 3 applies.

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 ("Selects this session's account (role)") and clarifies the split behavior: no arguments lists roles, with role logs in. The sibling list_accounts is never named, so an agent must infer the overlap between the zero-argument listing mode and that sibling rather than being routed explicitly.

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 clearly states both usage modes (call bare to list, pass role to select) and gives a hard precondition: "A role used by another session cannot be selected." It stops short of naming alternatives such as list_accounts or whoami, so the agent gets context but no explicit exclusions or redirects.

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