Skip to main content
Glama
Sign In
safe-mind-tools

safe-mind-tools

by lewo-media
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

safe_mind_register

Creates a new Safe Mind account and company for the legally required psychological risk assessment, then sends a 6-digit verification code by email so the account can be activated.

Instructions

Create a new Safe Mind account together with its company. Safe Mind runs the legally required psychological risk assessment (Gefährdungsbeurteilung psychischer Belastung, GBU Psyche) for German companies. Use this only when the user has no account yet; for an existing account go straight to safe_mind_get_api_key. No API key needed. Sends a 6-digit verification code to the email address and returns a confirmation message; the account is usable after safe_mind_verify_email. For privacy the answer is the same whether or not the address is already registered. Disposable (throwaway) email addresses are rejected with an error.

Input Schema

NameRequiredDescriptionDefault
emailYesWork email address of the person creating the account; receives the verification code.
lastNameYesLast name of the account owner.
passwordYesAccount password: at least 8 characters with an uppercase letter, a lowercase letter and a digit.
firstNameYesFirst name of the account owner.
companyNameYesLegal name of the company the assessment is for, e.g. "Muster GmbH".
employeeCountYesNumber of employees of the company; used for pricing and the survey participant limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / companyName / description
      Added value: +"Legal name of the company the assessment is for, e.g. \"Muster GmbH\"."
    • addedInput schema / properties / email / description
      Added value: +"Work email address of the person creating the account; receives the verification code."
    • addedInput schema / properties / employeeCount / description
      Added value: +"Number of employees of the company; used for pricing and the survey participant limit."
    • addedInput schema / properties / firstName / description
      Added value: +"First name of the account owner."
    • addedInput schema / properties / lastName / description
      Added value: +"Last name of the account owner."
    • addedInput schema / properties / password / description
      Added value: +"Account password: at least 8 characters with an uppercase letter, a lowercase letter and a digit."
  2. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/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 so well: it discloses the 6-digit email verification step, the dependency on safe_mind_verify_email before the account is usable, the privacy-preserving identical response for registered vs unregistered emails, and the disposable-email rejection error. These are non-obvious behaviors an agent could not infer from the schema.

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?

Front-loaded with the purpose in the first sentence, then domain context, routing rule, auth status, flow, and edge behavior. Every sentence adds operational value with no redundant restatement of the schema.

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?

For a six-required-parameter mutation tool with no annotations and no output schema, the description supplies the missing pieces: auth requirements, the multi-step verification flow, and the returned confirmation message. Nothing needed to call it correctly appears to be 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?

Schema description coverage is 100%, so the schema already documents all six parameters including password complexity, companyName format, and employeeCount's pricing/participant-limit purpose. The description adds little parameter-level detail beyond reiterating that the email receives the verification code, so the baseline 3 applies.

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+resource ('Create a new Safe Mind account together with its company') and distinguishes itself from sibling tools by naming safe_mind_get_api_key as the path for existing accounts. An agent can tell what this does and when it is not the right tool without opening the schema.

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?

Explicit when-to-use ('only when the user has no account yet') and an explicit alternative for the opposite case ('for an existing account go straight to safe_mind_get_api_key'). Also clarifies no API key is required, removing a common pre-call uncertainty.

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

Deploy Server

Other Tools