Skip to main content
Glama

set_student_password

Destructive

Set a learner's password directly, replacing their existing credentials. Use only when the user explicitly asks for this action; otherwise, send a password reset link instead.

Instructions

Set a learner's password directly. This is an ACCOUNT TAKEOVER primitive.

    `id` is the obfuscated Skilljar learner id, and `password` is the value to set.
    Whoever knows the value can then sign in as that person. The learner is not
    told, and their old password stops working.

    You must pass `confirm=True`. In almost every case `send_password_reset` is the
    correct tool: it emails the learner a link and never puts you in possession of
    their credentials. Use this one only when the user has explicitly asked to set a
    password directly and understands that.

    The password must satisfy the organization's policy. It is never echoed back and
    never appears in an error message.

    Requires the `students:manage-password` OAuth scope AND the `people.destructive`
    capability.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
confirmNo
passwordYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
noteYes
Install Server

TDQS

A5/5.0
Behavior5/5

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

Goes well beyond the destructiveHint annotation by disclosing that the learner is not notified, the old password stops working, the password is never echoed back or shown in errors, that confirm=True is mandatory, and the required OAuth scope and capability. This gives the agent a clear picture of the safety-critical behavior.

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 compact, front-loaded with the most important warning, and every sentence adds functional or safety-relevant information. There is no filler or repetition of schema-level details.

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?

The tool is a destructive, high-risk primitive, yet the description covers purpose, usage conditions, alternatives, required confirm flag, authentication requirements, side effects, and parameter semantics. The presence of an output schema means return-value documentation is not a gap. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 full responsibility for the parameters. It explains that `id` is the obfuscated Skilljar learner id, `password` is the value to set and must satisfy policy, and `confirm` must be passed as true. All three parameters receive meaningful semantic context.

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 the specific verb and resource: 'Set a learner's password directly.' The blunt warning 'This is an ACCOUNT TAKEOVER primitive' gives immediate clarity about the tool's true nature, and the naming of `send_password_reset` as the safer alternative distinguishes it from the closest sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'In almost every case send_password_reset is the correct tool' and narrows this tool's use to when 'the user has explicitly asked to set a password directly and understands that.' This is precise when-to-use and when-not-to-use guidance with a named alternative.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CloudSecurityAlliance/csa-skilljar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server