Skip to main content
Glama

Create Users

create_users
Destructive

Creates accounts from a user list and optionally adds new and existing users to a tag; existing emails are not recreated or password-changed, only tagged after confirmation.

Instructions

(Admin) Crea cuentas y, opcionalmente, las inscribe en una tag. Pide confirmación (no hay borrado de usuarios).

Los correos que ya existen NO se recrean ni se les cambia la clave (repitentes): solo se agregan a la tag.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "users": "<users>"
    },
    "name": "create_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
usersYeslista de {email, password, first_name?, last_name?, role?}. role por omisión STUDENT. Convención UTalca: clave = RUT sin puntos ni dígito verificador.
tag_idNotag a la que se agregan todos (nuevos y existentes). Opcional.
confirm_tokenNosolo en la segunda llamada, tras la confirmación del usuario.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the description is not the sole source of the safety profile. It adds genuinely useful behavior: the mandatory confirmation step before the second call, and the rule that existing accounts keep their password and are only tagged — a nuance an agent could not infer from the schema. There is mild tension between 'no hay borrado' and destructiveHint=true, but not a direct contradiction.

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?

Three short sentences, front-loaded with the admin scope and core action, then the confirmation requirement and the repeat-email rule. Every clause carries information; nothing 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?

Covers the two-step confirmation flow, admin gating and duplicate-email semantics for a mutation tool, and the existence of an output schema means return values need not be explained. A pointer to existence-checking siblings would close the remaining gap.

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 users, tag_id and confirm_token are already documented, including the convention that UTalca passwords equal the RUT without dots or check digit. The description only restates that tagging is optional and that repitentes are added to the tag, adding little meaning beyond the schema.

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?

States a specific verb and resource ('Crea cuentas') plus an optional side effect ('las inscribe en una tag') and an admin scope marker. It implicitly separates itself from add_students_to_tag and set_user_password by clarifying that existing emails are not recreated and passwords are not changed, though it never names an alternative tool.

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?

Gives clear operating context: admin-only, requires user confirmation, and describes the repitentes case so the agent knows a repeat call is not an error. It stops short of explicitly routing the agent to find_users first to check existence, so it is good context rather than full when/when-not guidance.

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